Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
Workflow Goal Still manually checking form responses in your inbox? What if every submission landed neatly in Airtable — and you got a clean Slack message instantly? That’s exactly what this wor...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.airtable, n8n-nodes-base.slack, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Baptiste Fort.
Original n8n.io sourceStill manually checking form responses in your inbox?
What if every submission landed neatly in Airtable — and you got a clean Slack message instantly?
That’s exactly what this workflow does.
No code, no delay — just a smooth automation to keep your team in the loop:
Tally → Airtable → Slack
Build an automated flow that:
A Webhook node in POST mode.
After connecting Tally, you now receive raw data inside a fields[] array.
Let’s convert that into something clean and structured.
Extract key info like Full Name, Email, Phone, etc. into simple keys.
Add a Set node to remap and clean the fields.
Use the data preview in the Webhook node to check the correct order.
Output
You now get clean data like:
{ "Full Name": "Jane Doe", "Email": "[email protected]", "Phone": "+123456789" }
✅ Once the data is cleaned, let’s store it in Airtable automatically.
Goal
Create one new Airtable row for each form submission.
What we’re setting up
An Airtable – Create Record node.
Technical
Output
Each submission creates a clean new row in your Airtable table.
⌛ After saving to Airtable, it’s a good idea to insert a short pause — this prevents actions like Slack messages from stacking too fast.
Goal
Wait a few seconds before sending a Slack notification.
What we’re setting up
A Wait node for X seconds.
✅ Technical
💬 Now that the record is stored, let’s send a Slack message to notify your team.
Goal Automatically alert your team in Slack when someone fills the form.
What we’re setting up
A Slack – Send Message node.
Technical
New lead received!
Name: {{$json["Full Name"]}}
Email: {{$json["Email"]}}
Phone: {{$json["Phone"]}}
Output
Your Slack team is notified instantly, with all lead info in one clean message.
Workflow Complete
Your automation now looks like this:
Tally → Clean → Airtable → Wait → Slack
Every submission turns into clean data, gets saved in Airtable, and alerts your team on Slack — fully automated, no extra work.
Looking for professional automation support? Try 0vni – Agence automatisation.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate a Tally form: store with Airtable, notify via Slack |
|---|---|
| Complexity | advanced |
| Nodes | 22 |
| Categories | Lead Generation |
| Author | Baptiste Fort |
| Published | 28 Jun 2025 |
Use the JSON export at /data/workflows/5437/5437.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Workflow Goal Still manually checking form responses in your inbox? What if every submission landed neatly in Airtable — and you got a clean Slack message instantly? That’s exactly what this wor...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Generation use case.