Rate limiting and waiting for external events
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Customer Datastore (n8n training) and Customer Messenger (n8n training).
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Customer Datastore (Customer Datastore (n8n training)): get all people
- SplitInBatches (Loop Over Items (Split in Batches)): loops over the items in batches
- Wait: waits 2 seconds
- Customer Messenger - Send message to client (Customer Messenger (n8n training)): uses Customer Messenger (n8n training)
- If: checks a condition and branches into true / false
- Create approval URL (Edit Fields (Set)): sets or maps fields
- Customer Messenger - Send URL to merchant (Customer Messenger (n8n training)): uses Customer Messenger (n8n training)
- Wait: pauses until webhook
Services it uses
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.
Rarely used nodes in this template: n8n-nodes-base.n8nTrainingCustomerMessenger
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - Wait
n8n-nodes-base.wait - No Operation, do nothing
n8n-nodes-base.noOp - Customer Datastore (n8n training)
n8n-nodes-base.n8nTrainingCustomerDatastore - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - If
n8n-nodes-base.if - Customer Messenger (n8n training)
n8n-nodes-base.n8nTrainingCustomerMessenger
From the author
Task: Control your data flow with rate limits and external cues Main use cases: - Control the rate of items flow into one or more services in your workflow - Wait for external events to occur before continuing with the rest of the workflow