Fetch & Split Parcel Scan Assignments via HTTP in n8n
Fetch & Split Parcel Scan Assignments via HTTP in n8n
Regular price
£8.99
Regular price
£8.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Fetch & Split Parcel Scan Assignments via HTTP in n8n
Regular price
£8.99
Regular price
£8.99
Sale price
Unit price
/
per
Fetch & Split Parcel Scan Assignments via HTTP in n8n
This starter workflow automatically fetches your n8n Community Weekly Challenge 07 parcel scan assignments from an n8n-hosted HTTP endpoint and splits the returned rows into individual scan items—ready for you to build your parcel count and total work units calculations.
What this workflow does
- Runs manually when you execute the workflow.
- Prompts you to set your forum username and participant key for the run (stored in “My settings”).
- Sends an HTTP GET request to the n8n Community Weekly Challenge 07 data endpoint:
- Your username is passed as a query parameter.
- Your participant key is sent in the x-participant-key header.
- Splits the returned rows array into individual scan items so downstream logic can calculate values per scan.
- Provides two disconnected placeholders where you add your own native logic to output:
- parcel_count (Question 1)
- total_units (Question 2)
Use cases
- Build a clean n8n approach to consume Community Weekly Challenge 07 assignment data via HTTP.
- Develop and test your own calculations using split scan rows as the input dataset.
- Use as a reference for secure parameter passing (username query + participant key header) in n8n HTTP Request setups.
Technical details
- Nodes used: Manual Trigger, Set, HTTP Request, Split Out, Sticky Note.
- Endpoint guidance: participation setup is at https://marketing.app.n8n.cloud/webhook/cwc/challenge-07. Importing the starter alone does not start your timer—first personal-data request starts it.
- Export cleanup: after testing, export a clean copy and clear participantKey, remove passwords, credential references, and save.
