Automate a Tally form: store with Airtable, notify via Slack
🎯 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 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:
- receives Tally form submissions,
- cleans up the data into usable fields,
- stores the results in Airtable,
- and automatically notifies a Slack channel.
Step 1 – Connect Tally to n8n
What we’re setting up
A Webhook node in POST mode.
Technical
- Add a Webhook node.
- Set it to POST.
- Copy the generated URL.
- In Tally → Integrations → Webhooks → paste this URL.
- Submit a test response on your form to capture a sample structure.
Step 2 – Clean the data
After connecting Tally, you now receive raw data inside a fields[] array.
Let’s convert that into something clean and structured.
Goal
Extract key info like Full Name, Email, Phone, etc. into simple keys.
What we’re doing
Add a Set node to remap and clean the fields.
Technical
- Add a Set node right after the Webhook.
- Add new values (String type) manually:
- Name: Full Name → Value: {{$json["fields"][0]["value"]}}
- Name: Email → Value: {{$json["fields"][1]["value"]}}
- Name: Phone → Value: {{$json["fields"][2]["value"]}}
(Adapt the indexes based on your form structure.)
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": "jane@example.com", "Phone": "+123456789" }
Step 3 – Send to Airtable
✅ 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
- Add an Airtable node.
- Authenticate or connect your API token.
- Choose the base and table.
- Map the fields:
- Name: {{$json["Full Name"]}}
- Email: {{$json["Email"]}}
- Phone: {{$json["Phone"]}}
Output
Each submission creates a clean new row in your Airtable table.
Step 4 – Add a delay
⌛ 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
- Add a Wait node.
- Choose Wait for X minutes.
Step 5 – Send a message to Slack
💬 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
- Add a Slack node.
- Connect your account.
- Choose the target channel, like #leads.
- Use this message format:
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.
Automate a Tally Form Store with Airtable and Notify via Slack
This n8n workflow automates the process of storing data submitted via a Tally form into Airtable and then sending a notification to a Slack channel. It's designed to simplify data collection and team communication for new entries.
What it does
This workflow performs the following key steps:
- Triggers on a Schedule: The workflow is set to run at regular intervals (e.g., every hour, daily, etc.) to check for new data.
- Fetches Data from Airtable: It connects to your specified Airtable base and table to retrieve records. This is likely intended to fetch new submissions or process existing ones.
- Sends Notification to Slack: After fetching data from Airtable, the workflow posts a message to a designated Slack channel. This can be used to notify a team about new entries, updates, or any other relevant information pulled from Airtable.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Airtable Account: With an existing base and table where your Tally form submissions are stored or will be stored.
- Airtable Credentials: An API key or personal access token for n8n to connect to your Airtable account.
- Slack Account: With a channel where you want to send notifications.
- Slack Credentials: A Slack API token or webhook URL for n8n to post messages.
Setup/Usage
-
Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, click on "Workflows" in the left sidebar.
- Click "New" and then "Import from JSON".
- Paste the JSON content or upload the file.
-
Configure Credentials:
- Click on the "Airtable" node and add your Airtable credentials. You'll need to specify your Base ID and Table Name.
- Click on the "Slack" node and add your Slack credentials. Configure the channel and message content as desired.
-
Configure Schedule Trigger:
- Click on the "Schedule Trigger" node.
- Set the desired interval for how often you want the workflow to run (e.g., every 5 minutes, every hour, once a day).
-
Activate the Workflow:
- Once all credentials and configurations are set, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
This workflow provides a solid foundation for integrating Tally form submissions with Airtable and Slack. You might want to enhance it further by adding nodes to:
- Actually receive Tally form submissions (e.g., via a Webhook node).
- Filter or transform data before sending it to Airtable or Slack.
- Conditionally send Slack notifications based on the content of the Airtable record.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte