Analyze Event Scans & Kit Pickups with n8n HTTP Webhooks

Find the answers behind event scans and kit pickups—automatically in n8n

This starter n8n Community Challenge 04 workflow fetches event case, scan, and kit datasets from an n8n-hosted HTTP API, helps you compute three challenge answers (first accepted scan, busiest session, and uncollected kits), and can optionally submit your results back for validation.

What this workflow does

• Runs manually to start the challenge workflow.
• Stores required settings: your participant username, participant key, and the challenge API base URL.
• Retrieves datasets via HTTP:
  • Fetches case data and the scans dataset.
  • Splits scans into individual rows so you can filter and aggregate to find the earliest ACCEPTED scan for Stage 1 and determine the busiest session for Stage 2.
• Uses your Stage 2 result to request the kits dataset for that session, then splits it into kit rows for Stage 3.
• Guides Stage 3 summarization: you filter and summarize kit rows to count CONFIRMED attendees who requested a kit but have not picked it up.
• Optional validation: each Stage answer can be posted to the challenge API check endpoint (disabled by default).

Use cases

• Automation engineers prototyping HTTP-driven data pipelines in n8n.
• SaaS operators or internal teams analyzing operational data: scan acceptance timing, session demand, and uncollected kit counts.
• Participants completing n8n Community Challenge 04 with a guided starter workflow.

Technical details

• Nodes used: Manual Trigger, HTTP Request, Set, Split Out, Sticky Note.
• Authentication: enter username/key in Settings; in the private preview environment, add HTTP Basic Auth to each HTTP Request node.
• Implementation focus: build missing filter/sort/grouping logic with native n8n nodes and map outputs into Stage 1/2/3 answer fields.