COMMUNITY WEEKLY CHALLENGE
A community shop has 30 parcel requests. Separate the requests that need correction from those ready for express or standard delivery, then count each queue.
One batch. Three answers. Count requests, not parcels.GETTING STARTED
The starter fetches your requests. You add the routing and counting.
Register once with your forum username and email, or reuse your existing key. Keep the key private.
Create your accountUse the template page to import the starter into your n8n editor. Fill in your username and participant key in Settings. Your first successful personal data fetch starts the timer.
Open starter template ↗Use native nodes to route requests, count each queue, and map your computed counts directly to the three Number answers.
Read the three questionsYour existing account and key carry forward. Your recorded challenge history stays with you.
THE BRIEF · CHALLENGE 05
One personal batch. Three independent request counts.
You receive exactly 30 requests in rows[]. Each has a unique request_id. Re-fetching returns the same personal batch without resetting the timer.
contact_email is a nonempty fictional address or exactly "", with no missing, null or whitespace-only values. parcel_count is an integer from 0 to 4. delivery is exactly EXPRESS or STANDARD.
EXPRESS sends the valid request to Express ready.A request with both invalid conditions counts once. A request with four parcels also counts once. Every batch has all three queues.
Needs correction
Count requests whose contact email is empty OR whose parcel count is zero. Apply this rule before the delivery branch. A request with both problems counts once.
Return: A whole number from 0 to 30.
Validate first, then count request_id.Express ready
Count valid requests whose delivery is EXPRESS. An express request with a missing email or zero parcels belongs in Needs correction.
Return: A whole number from 0 to 30.
Use the valid branch, then count request_id.Standard ready
Count the remaining valid requests with STANDARD delivery. Every request belongs to exactly one queue, even if it contains several parcels.
Return: A whole number from 0 to 30.
Use the remaining valid branch, then count request_id.The correct counts add up to 30. This checks the total, but does not prove the routing is right.
Fill in username and key in Settings. Keep the supplied base URL and HTTP Authentication None. The starter sends the key in the header, never in the URL.
GET https://marketing.app.n8n.cloud/webhook/cwc/challenge-05/data?file=requests&username=YOUR_USERNAME
x-participant-key: YOUR_KEYYour first successful personal fetch starts the clock. Fetch before using an optional answer check. Checks do not stop the timer.
THE RULES
Correct eligible answers reach the leaderboard automatically. Workflow review happens at season end before rewards.
No Code, Function, AI, Agent, MCP, or Tool nodes. Use native nodes for filtering, sorting, deduplication, and counting.
Build, solve and explain the challenge yourself. AI assistance of any kind is not allowed, including help with planning, generating, debugging or explaining your workflow and answers. Hardcoded answers, pinned data and code hidden in expressions do not qualify.
Correct answers and a rules-compliant export count immediately. Each challenge awards 15 points for the fastest completion, 12 for second and third, and 11 for the rest. Workflows are checked at season end before rewards are distributed.
Use Summarize to Count request_id and map each answer directly from its computed count. Keep the trigger, data fetch, routing and answer nodes enabled and connected. Use forward routing for one batch. Loops, grouped summaries, answer arithmetic, hardcoded values and disconnected processing do not qualify.
Your first correct final submission retains the three counts, sanitized export, explanation and finish time. A retry returns the original accepted receipt and cannot replace its evidence or reset the timer.
Build, solve and explain your workflow without AI assistance of any kind. Fast completion alone is not proof of AI use. Exact millisecond ties share the same competition rank.