Analyze event scans and kit pickups with HTTP webhooks
Ready for 3.0What this workflow does
This workflow has 13 nodes and runs manually, when you click “Execute workflow”. It uses only n8n's built-in nodes.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Settings (Edit Fields (Set)): sets 3 fields: username, key, base
- Open your case (HTTP Request): calls an HTTP API
- Get scans (HTTP Request): calls an HTTP API
- Scan rows (Split Out): splits a list into separate items
- Stage 2 answer (Edit Fields (Set)): sets 1 field: b2
- Check stage (HTTP Request): calls an HTTP API (POST)
- Get kits (HTTP Request): calls an HTTP API
- Kit rows (Split Out): splits a list into separate items
- Stage 1 answer (Edit Fields (Set)): sets 1 field: b1
- Check stage (HTTP Request): calls an HTTP API (POST)
…plus 2 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut
From the author
Quick overview This starter workflow for n8n Community Challenge 04 fetches case, scan, and kit datasets from an n8n-hosted HTTP API, then guides you to compute three answers (first accepted scan, busiest session, and uncollected kits) and optionally submit…