Count & Validate Parcel Requests via HTTP Webhooks in n8n

Count and validate your Challenge 05 parcel requests in n8n using HTTP webhooks

This 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 /check endpoint.

What this workflow does

• Manual execution: Runs when you click the manual trigger.
• Configures API context: Stores your forum username, participant key, and the challenge base URL used for API calls.
• Fetches your dataset: Sends an HTTP GET request to the Community Weekly Challenge endpoint to retrieve your requests data file for your username.
• Splits into request items: Splits the returned JSON into 30 individual request items from the rows array.
• Provides placeholders for counting: You add the routing/validation logic and calculate three counts:
  • Needs correction
  • Express ready
  • Standard ready
  Then place the results into Stage 1 (b1), Stage 2 (b2), and Stage 3 (b3) as numbers.
• Optional answer validation: The workflow can post each stage’s answer to the /check endpoint to validate results—disabled by default.

Use cases

• Automation engineers prototyping Challenge-style data workflows with n8n.
• SaaS operators testing how to structure API fetch → split → compute → validate pipelines.
• Challenge participants validating parcel request counts quickly without manual spreadsheet work.

Technical details

• n8n nodes: Manual Trigger, Set, Split Out, Sticky Note, HTTP Request.
• HTTP integration: Calls the Community Weekly Challenge API endpoint to fetch request data, then (optionally) uses the /check endpoint for validation.
• Authentication handling: Keep HTTP request authentication set to None so the participant key is sent only in the x-participant-key header.