Route documents: Google Sheets
Starts when someone submits the form across Google Sheets, Outlook and Slack, routes each kind of record down its own branch, then drops anything it has already handled. Built for task routing, around a "Keep Valid Tasks" step, in 23 documented nodes.
Route documents with Outlook and MySQL on autopilot. An original, ready-to-import n8n workflow built around the 'Approval Workflow' pattern for software development & devops. It starts from a form and orchestrates 23 nodes across Google Sheets, Outlook, Slack. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.
Key benefits
- ✓Keeps Google Sheets and Outlook in step for task routing, without anyone re-typing a row
- ✓Safe to re-run: records already in Google Sheets or Outlook are skipped, across all 23 nodes of this task-routing build
- ✓A failed Google Sheets or Outlook call is retried rather than dropped, at any of the 23 nodes in this task-routing build
- ✓Branches rejoin before Google Sheets, so a task-routing run reports once rather than 23 times
- ✓Every task-routing run leaves an audit row behind, alongside Google Sheets
Use cases
- →Teams keeping Google Sheets and Outlook aligned by hand for task routing
- →Intake checked for completeness before it is stored in Google Sheets, for task routing
- →Task routing work where "Keep Valid Tasks" is still a manual step before Google Sheets
- →Task routing work that only reaches Google Sheets when a form is submitted, when someone remembers to start it
Integrations
Workflow preview (23 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (23 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Branching cleanly on approve versus decline
- •Moving data between Google Sheets, Outlook and MySQL in a single run
- •Splitting one run into branches and merging the results back
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Google Sheets, Outlook, Slack, HTTP / REST API, …). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Route expenses with Slack & MySQL
Standups on n8n: runs when a form is submitted across Slack, MySQL, Outlook and Google Sheets, starting at "Stamp & Shape Task". 21 documented nodes.
Route requests: Outlook
Onboarding on n8n: runs when a form is submitted across Outlook, Notion, Slack, Google Sheets and MySQL, starting at "Keep Valid Tasks". 32 documented nodes.
Archive the database: Google Sheets, scheduled
Data transforms on n8n: runs on a schedule across Google Sheets, Slack, MySQL and Outlook, starting at "Fetch Changes Since Watermark". 21 documented nodes.
Snapshot the database: MySQL
Helpers on n8n: runs on a schedule across MySQL, Slack, Google Sheets and Outlook, starting at "Fetch Changes Since Watermark". Branches on the check before anything is written. 23 documented nodes.