Categorize receipts: MySQL
Watches an inbox across MySQL, Microsoft Teams and Slack, rolls the rows up into a few numbers, then runs the custom logic in a Code node. Built for approvals, around a "Gather from MySQL" step, in 17 documented nodes.
Categorize receipts with MySQL and Microsoft Teams. An original, ready-to-import n8n workflow built around the 'Expense Tracking' pattern for finance & banking. It triggers on new email and orchestrates 17 nodes across MySQL, Microsoft Teams, Slack. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. What used to take a morning now runs on its own.
Key benefits
- ✓Keeps MySQL and Microsoft Teams in step for approvals, without anyone re-typing a row
- ✓A failed MySQL or Microsoft Teams call is retried rather than dropped, at any of the 17 nodes in this approvals build
- ✓Branches rejoin before MySQL, so a approvals run reports once rather than 17 times
- ✓Every approvals run leaves an audit row behind, alongside MySQL
- ✓Fans the same result out to Slack in the same run, for approvals
Use cases
- →Teams keeping MySQL and Microsoft Teams aligned by hand for approvals
- →Approvals work where "Gather from MySQL" is still a manual step before MySQL
- →Approvals work that only reaches MySQL when mail lands in the inbox, when someone remembers to start it
Integrations
Workflow preview (17 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (17 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
Advanced levelAdds branching depth and audit logging on top of the core pattern.
- •Validating before writing to the ledger
- •Flagging anomalies for review
- •Moving data between IMAP email, MySQL and Microsoft Teams in a single run
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 (MySQL, Microsoft Teams, Slack). 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
Reconcile transactions: Slack
Approvals on n8n: runs when mail lands in the inbox across Slack, Google Sheets, MySQL and Microsoft Teams, starting at "Keep Valid Invoices". 23 documented nodes.
Digest long emails with Slack and MySQL
Newsletters on n8n: runs when a webhook arrives across Slack, MySQL and Microsoft Teams, starting at "Normalize Email Payload". Scores the sentiment of every message. 19 documented nodes.
Nurture leads: Google Sheets & MySQL
Newsletters on n8n: runs on a schedule across Google Sheets, MySQL, Slack and Microsoft Teams, starting at "Read Pending Queue (Google Sheets)". 22 documented nodes.
Summarize documents for contracts
Contracts on n8n: runs when a webhook arrives across Google Sheets, Microsoft Teams, Slack and MySQL, starting at "Normalize Document Payload". 23 documented nodes.