Fetch and split parcel scan assignments with HTTP Request in n8n

Quick overview

This starter workflow for n8n Community Weekly Challenge 07 fetches your personal assignment and a set of parcel scan rows from an n8n-hosted HTTP endpoint, then splits the rows into individual scan items so you can build two calculations (parcel count and total work units).

How it works

1. Runs manually when you execute the workflow.
2. Sets your forum username and participant key for the run.
3. Sends an HTTP GET request to the n8n Community Weekly Challenge 07 data endpoint with your username as a query parameter and your participant key in the x-participant-key header.
4. Splits the returned rows array into individual scan items for downstream processing.
5. Leaves two disconnected placeholders where you add your own native logic to compute and output parcel_count (Question 1) and total_units (Question 2).

Setup

1. Check participation dates at https://marketing.app.n8n.cloud/webhook/cwc/challenge-07 and create or recover your participant account there. The permanent personal-data endpoint is available when C07 opens; importing this starter alone does not start your timer.
2. Enter your exact community username and current participant key in My settings. Run the shared fetch path when you are ready. The first personal data issue starts the clock, and later fetches retain the original assignment and start.
3. Build and test your own native calculations, then export a clean copy. Clear participantKey and remove passwords, credential references, saved run data and pinned data. Submit both integers, your JSON and your own explanation at https://marketing.app.n8n.cloud/webhook/cwc/challenge-07/submit.

Requirements

• n8n with Manual Trigger, Edit Fields, HTTP Request and Split Out. The setup path was verified on n8n 2.35.5 and 2.43.7. A current CWC account is required when participation is open.

Customization

• Use your returned personal selection rule and desk to build the missing native-node calculation. Both answer cards use the same 24 scans; no second HTTP request or supplied calculation is included.

Additional info

This is an intentionally unfinished starter for Community Weekly Challenge 07, The Exception Desk, and the Season 2 finale. No ranked solution or answer is supplied. AI assistance is not allowed for challenge entries. Code, Function and Function Item nodes are prohibited, including disabled or disconnected nodes. Explain your own approach in 40 to 2,000 characters and at least eight words. Correct eligible submissions are accepted automatically. Uploaded workflows remain private and are not executed by the challenge service. C07 is being prepared for launch; check the challenge website for participation dates.