{"product_id":"count-validate-parcel-requests-via-http-webhooks-in-n8n","title":"Count \u0026 Validate Parcel Requests via HTTP Webhooks in n8n","description":"\u003ch3\u003eCount and validate your Challenge 05 parcel requests in n8n using HTTP webhooks\u003c\/h3\u003e\n\u003cp\u003eThis starter n8n workflow pulls your personal Challenge 05 parcel-request dataset from n8n’s Community Weekly Challenge API, splits it into individual request items, and gives you ready-to-fill Stage 1\/2\/3 counts—optionally validating each answer via the challenge \u003ccode\u003e\/check\u003c\/code\u003e endpoint.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eManual execution:\u003c\/strong\u003e Runs when you click the \u003cem\u003emanual trigger\u003c\/em\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eConfigures API context:\u003c\/strong\u003e Stores your forum username, participant key, and the challenge base URL used for API calls.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eFetches your dataset:\u003c\/strong\u003e Sends an HTTP GET request to the Community Weekly Challenge endpoint to retrieve your \u003cem\u003erequests\u003c\/em\u003e data file for your username.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSplits into request items:\u003c\/strong\u003e Splits the returned JSON into \u003cstrong\u003e30\u003c\/strong\u003e individual request items from the \u003ccode\u003erows\u003c\/code\u003e array.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eProvides placeholders for counting:\u003c\/strong\u003e You add the routing\/validation logic and calculate three counts:\n    \u003cul\u003e\n      \u003cli\u003e\u003cstrong\u003eNeeds correction\u003c\/strong\u003e\u003c\/li\u003e\n      \u003cli\u003e\u003cstrong\u003eExpress ready\u003c\/strong\u003e\u003c\/li\u003e\n      \u003cli\u003e\u003cstrong\u003eStandard ready\u003c\/strong\u003e\u003c\/li\u003e\n    \u003c\/ul\u003e\n    Then place the results into \u003cstrong\u003eStage 1 (b1), Stage 2 (b2), and Stage 3 (b3)\u003c\/strong\u003e as numbers.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eOptional answer validation:\u003c\/strong\u003e The workflow can post each stage’s answer to the \u003ccode\u003e\/check\u003c\/code\u003e endpoint to validate results—\u003cstrong\u003edisabled by default\u003c\/strong\u003e.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eAutomation engineers prototyping Challenge-style data workflows with n8n.\u003c\/li\u003e\n  \u003cli\u003eSaaS operators testing how to structure API fetch → split → compute → validate pipelines.\u003c\/li\u003e\n  \u003cli\u003eChallenge participants validating parcel request counts quickly without manual spreadsheet work.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n nodes:\u003c\/strong\u003e Manual Trigger, Set, Split Out, Sticky Note, HTTP Request.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eHTTP integration:\u003c\/strong\u003e Calls the Community Weekly Challenge API endpoint to fetch request data, then (optionally) uses the \u003ccode\u003e\/check\u003c\/code\u003e endpoint for validation.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAuthentication handling:\u003c\/strong\u003e Keep HTTP request authentication set to \u003cstrong\u003eNone\u003c\/strong\u003e so the participant key is sent only in the \u003ccode\u003ex-participant-key\u003c\/code\u003e header.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46206053646515,"sku":"N8N-20778","price":21.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/bi4eSegjYoItGdWmmxWQw_5vVXyC8w.png?v=1791796201","url":"https:\/\/buyflowscripts.com\/products\/count-validate-parcel-requests-via-http-webhooks-in-n8n","provider":"N8N Commerce","version":"1.0","type":"link"}