Handling common workflow scenarios in n8n means designing automations that match how real work actually happens. Most business processes need decisions, approvals, routing to the right people, and alerts when something important occurs. n8n supports these scenarios using triggers, conditions, branching, and notifications.
Approvals (getting a yes/no before the next step)
Approval workflows typically follow this pattern: request → review → approve/reject → action.
In n8n, you can automate approvals by:
- sending an approval request to email or Slack with key details
- capturing the decision through a webhook, form link, or a response-based trigger
- using an IF/Switch node to continue the workflow based on “Approved” or “Rejected”
- recording the decision in a sheet/CRM and notifying the requester
Example: Expense request above a threshold goes to a manager for approval before payment processing.
Routing (sending tasks to the right team)
Routing means directing work based on rules such as category, region, priority, or department.
You can route using Switch, filters, and branching paths:
- Sales leads by location to different sales reps
- Support tickets by category to specific queues
- HR queries to the correct specialist
Alerts (notifying when action is needed)
Alerts are used when you want immediate attention:
- workflow failures or retries
- urgent tickets, high-value leads, payment issues
- thresholds crossed (inventory low, budget exceeded)
You can send alerts via Slack, email, SMS, or dashboards, and include context from the workflow so the receiver can act quickly.
These patterns make workflows practical, reliable, and aligned with real operational needs.
