Process uploaded files with Slack & MySQL
Runs on a schedule across Slack, MySQL and Google Drive, branches on the check before anything is written, then writes the result out as a file. Built for contracts, around a "Export All Rows (MySQL)" step, in 18 documented nodes.
Process uploaded files with Google Drive and MySQL. An original, ready-to-import n8n workflow built around the 'File Processing' pattern for legal & compliance. It runs on a schedule and orchestrates 18 nodes across Slack, MySQL, Google Drive. 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. Your team sees the right data at the right time.
Key benefits
- ✓Keeps Slack and MySQL in step for contracts, without anyone re-typing a row
- ✓A failed Slack or MySQL call is retried rather than dropped, at any of the 18 nodes in this contracts build
- ✓Every contracts run leaves an audit row behind, alongside Slack
- ✓Fans the same result out to Google Drive in the same run, for contracts
- ✓Pinned sample data ships with it — run all 18 nodes for contracts before wiring Slack
Use cases
- →Teams keeping Slack and MySQL aligned by hand for contracts
- →Contracts work where "Export All Rows (MySQL)" is still a manual step before Slack
- →Contracts work that only reaches Slack on a schedule, when someone remembers to start it
Integrations
Workflow preview (18 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (18 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.
- •Serializing processed items back out to a file
- •Quarantining malformed rows without failing the whole batch
- •Archiving the processed file
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 (Slack, MySQL, Google Drive). 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
Extract from receipts with Slack for contracts
Contracts on n8n: runs on a schedule across Slack, Google Drive and MySQL, starting at "List Changed Docs (Google Drive)". Looks the answer up in a vector store. 16 documented nodes.
Extract from receipts: MySQL
Contracts on n8n: runs on a schedule across MySQL, Slack and Google Drive, starting at "Download from Google Drive". Parses the incoming file into rows. 16 documented nodes.
Extract from uploaded files: Google Drive for contracts
Contracts on n8n: runs on a schedule across Google Drive, Slack, Google Sheets and MySQL, starting at "List Changed Docs (Google Drive)". Looks the answer up in a vector store. 32 documented nodes.
Process documents: Slack & MySQL
Contracts on n8n: runs on a schedule across Slack, MySQL and Google Drive, starting at "Export All Rows (MySQL)". Branches on the check before anything is written. 19 documented nodes.