Save form submissions: Google Sheets & MySQL
Starts when someone submits the form across Google Sheets, MySQL and Slack, routes each kind of record down its own branch, then drops anything it has already handled. Built for auto-responders, around a "Normalize Email Payload" step, in 23 documented nodes.
Save form submissions with MySQL and Microsoft Teams end to end. An original, ready-to-import n8n workflow built around the 'Form Intake' pattern for marketing & advertising. It starts from a form and orchestrates 23 nodes across Google Sheets, MySQL, Slack. 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 Google Sheets and MySQL in step for auto-responders, without anyone re-typing a row
- ✓Safe to re-run: records already in Google Sheets or MySQL are skipped, across all 23 nodes of this auto-responders build
- ✓A failed Google Sheets or MySQL call is retried rather than dropped, at any of the 23 nodes in this auto-responders build
- ✓Branches rejoin before Google Sheets, so a auto-responders run reports once rather than 23 times
- ✓Every auto-responders run leaves an audit row behind, alongside Google Sheets
Use cases
- →Teams keeping Google Sheets and MySQL aligned by hand for auto-responders
- →Intake checked for completeness before it is stored in Google Sheets, for auto-responders
- →Auto-responders work where "Normalize Email Payload" is still a manual step before Google Sheets
- →Auto-responders 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.
- •Serving an n8n-hosted form and shaping each submission
- •Validating required fields before anything is written
- •Moving data between MySQL, Microsoft Teams and Google Sheets 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 (Google Sheets, MySQL, 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
Send a weekly summary with MySQL
Auto-responders on n8n: runs on a schedule across MySQL, Microsoft Teams, Google Sheets and Slack, starting at "Read Source Feed". Runs the text through an AI chain. 24 documented nodes.
Follow up open deals with Slack and Google Sheets
Auto-responders on n8n: runs on a schedule across Slack, Google Sheets, MySQL and Microsoft Teams, starting at "Read Pending Queue (MySQL)". 14 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.
Follow up for newsletters
Newsletters on n8n: runs on a schedule across Google Sheets, Slack, Microsoft Teams and MySQL, starting at "Score the Lead". Routes each kind of record down its own branch. 23 documented nodes.