COMMUNITY WEEKLY CHALLENGE
Scanners retry. Some check-ins are rejected. Work out who arrived first, which room was busiest, and how many kits are still waiting.
The starter already fetches the files. Your job is to add the native nodes.GETTING STARTED
The request nodes are already in the starter. You bring the logic.
Register with your forum username and email. Your key lets n8n fetch your own dataset.
Create your accountUse the template page to import the starter into your n8n editor. Fill in your username and participant key in Settings.
Open starter template ↗Read the three questions below. Add native nodes, check each result, then submit your exported workflow JSON.
Read the three questionsYour existing account and key work here. No need to register again.
THE BRIEF · CHALLENGE 04
Two JSON files, three short questions. Start with scans, then use your Stage 2 result to fetch kits.
The workshop doors are open. Scanners retry, some check-ins are rejected, and attendees are heading to different rooms. At the kit desk, not everyone has collected what they requested.
Your job is to find three useful answers in those records. Every timestamp is a complete UTC date ending in Z. No CSV, pagination, or time-zone conversion to configure.
First through the door
Use scans.rows. Keep status = ACCEPTED, sort the full at timestamp from earliest to latest, and take the first attendee_id. The rows arrive in a shuffled order.
Return: An attendee ID matching AT- followed by 5 uppercase letters or digits 2–9.
Split Out → Filter → Sort → LimitMost popular room
Keep accepted scans and remove repeated attendee_id values. Count attendees by session, then take the session with the largest count. Each attendee has accepted scans for only one session. The top session is unique.
Return: A session ID matching WS- followed by 4 uppercase letters or digits 2–9.
Filter → Remove Duplicates → Summarize → Sort → LimitKits still waiting
Fetch kits with the Stage 2 session. Count rows where registration_status = CONFIRMED, requested_kit = true, and picked_up = false. There is one roster row per attendee.
Return: A whole number from 0 to 99.
HTTP Request → Split Out → Filter → SummarizeThe starter has these request nodes ready. Fill in username and key in Settings, then run the case and scans requests. Your key is sent in the x-participant-key header, not the URL.
GET https://marketing.app.n8n.cloud/webhook/cwc/challenge-04/data?file=scans&username=YOUR_USERNAME
x-participant-key: YOUR_KEYFor kits, use file=kits and session= with your computed Stage 2 value. A well-formed session still returns a roster even when it is not the busiest one. A successful fetch does not confirm Stage 2.
Your export is replayed on three independent unseen datasets. An accepted submission stays pending and adds no points until that replay is verified. A replay system fault keeps it pending for review.
THE RULES
The rules check tells you which node or expression needs changing before you submit.
No Code, Function, AI, Agent, MCP, or Tool nodes. Use native nodes for filtering, sorting, deduplication, and counting.
Submit your own exported workflow and a short explanation. AI help with design is allowed. Hardcoded answers, pinned data, and code hidden in expressions do not qualify.
Correct answers enter pending replay. The workflow must pass three unseen workshop shifts before 11 points count.
A LITTLE HELP, IF YOU NEED IT
The n8n Academy covers the foundations. Our practice lessons give you a small place to try them. Bring your questions back to the community.