Why Automate Airtable-to-Slack Notifications?
If your team lives in Slack and your data lives in Airtable, you already know the pain: someone updates a record, moves a project to "In Review," or adds a new lead — and nobody finds out until the next standup. Manual status checks drain time and create bottlenecks.
Connecting Airtable to Slack with an automation tool like Make.com (formerly Integromat) eliminates that gap entirely. Every time a record changes in Airtable, your team gets an instant, formatted Slack message — no copy-pasting, no manual pings, no missed updates.
This guide walks you through exactly how to set up this integration, step by step, with no code required.
What You'll Need
Before you start, make sure you have:
An Airtable account (free tier works) with a base you want to monitor
A Slack workspace where you have permission to add apps
A Make.com account (the free plan includes 1,000 operations/month — enough to get started)
That's it. No developers, no APIs to authenticate manually, no webhooks to configure by hand.
Overview: How the Automation Works
Here's the flow you're building:
A record in Airtable is created or updated (the trigger)
Make.com detects the change
Make.com formats the data and sends a message to your chosen Slack channel
Your team sees the update in real time
Make.com acts as the middleware — it watches Airtable and speaks to Slack on your behalf. This type of workflow is called a Scenario in Make.com terminology.
Step 1: Create Your Make.com Account
Go to Make.com and sign up for a free account. The free plan gives you 1,000 operations per month and two active scenarios, which is plenty for this integration.
Once you're in, click Create a new scenario in the top right corner of your dashboard.
Step 2: Add the Airtable Trigger Module
In the scenario editor, click the large + button to add your first module. Search for Airtable and select it from the app list.
Choose the trigger type: Watch Records. This trigger fires every time a record is created or updated in a specific Airtable view.
Make.com will prompt you to connect your Airtable account. Click Add and authorize access. You'll be redirected to Airtable to grant permissions — click Allow access.
Once connected, configure the trigger:
Base: Select the Airtable base you want to monitor
Table: Choose the specific table
View: Pick the view (you can use a filtered view to only watch specific records — for example, only records where Status = "In Review")
Limit: Start with 10 records per poll to keep operations low
Click OK to save the module.
Pro Tip: Use a Dedicated Airtable View
Create a dedicated view in Airtable just for this automation — for example, "Make Sync View." Filter it to only show records you actually want to trigger Slack notifications. This prevents noise (you don't need a Slack ping every time someone edits a typo in an internal note).
Step 3: Add the Slack Action Module
Click the + button after your Airtable trigger to add the next module. Search for Slack.
Select Create a Message as the action type.
Connect your Slack account by clicking Add and authorizing Make.com to post to your workspace. You'll need to be a workspace admin or have permission to install apps.
Configure the Slack message:
Channel: Choose the Slack channel where notifications should go (e.g., #project-updates or #sales)
Text: This is where it gets powerful — you can use Airtable field values dynamically
Building the Slack Message with Dynamic Fields
In the Text field, click anywhere inside the input box. Make.com shows a panel on the right with all the available data from your Airtable trigger — every field from that record.
Build a message like this:
New update in Airtable
Record: [Name field from Airtable]
Status: [Status field from Airtable]
Assigned to: [Assignee field from Airtable]
Updated at: [Last modified time]
View record: [Airtable record URL]
Click on each bracket placeholder and select the corresponding Airtable field from the panel. Make.com will substitute the real values when the scenario runs.
You can also use Slack's formatting:
Wrap text in asterisks for bold: New update in Airtable
Use > at the start of a line for a blockquote callout
Add emoji for quick visual scanning: ✅ Status: Done, 🔴 Status: Blocked
Step 4: Set the Schedule (Polling Interval)
Make.com's free plan uses polling — it checks Airtable on a schedule rather than instantly. Click the clock icon at the bottom of your scenario to set how often it checks.
Options range from every 15 minutes to once a day. For most teams, every 15 minutes is the right balance between responsiveness and operation usage.
If you need real-time triggers (instant notifications the moment a record changes), you'll need Make.com's Core plan and Airtable's webhook feature — but for most use cases, 15-minute polling is indistinguishable from real-time in practice.
Step 5: Test the Scenario
Before activating, test it. Click Run once in the bottom left corner of the scenario editor.
Go to your Airtable base and either create a new record or update an existing one in your monitored view. Wait a moment, then check your Slack channel.
You should see your formatted message arrive. If not, Make.com's execution log (the numbered bubbles on each module) will show exactly where it failed and what data was passed.
Common issues:
Wrong view selected: Make sure the record you updated is actually in the view you selected in the trigger
Slack permissions: The Make.com app must have permission to post to your chosen channel (for private channels, you need to invite the Make.com bot first: /invite @Make)
Empty fields: If an Airtable field is empty, the dynamic placeholder will output nothing — consider adding a fallback like "Not assigned" using Make.com's if() function
Step 6: Activate the Scenario
Once your test passes, toggle the scenario from OFF to ON using the switch at the bottom of the editor. Make.com will now poll Airtable on your chosen schedule automatically — no browser tab required, no scripts running on your computer.
Advanced: Add Filters and Conditions
The basic scenario sends a Slack message for every new or updated record. That might be too much noise. Make.com lets you add filters between modules — conditions that must be true before the next module runs.
To add a filter, click the small funnel icon on the arrow between your Airtable and Slack modules.
Example filters:
Only notify when Status changes to "Blocked" (catch urgent issues before they fall through the cracks)
Only notify when Assignee is a specific person (personal task notifications)
Only notify when Priority is "High" or "Critical"
Only notify on newly created records (ignore edits)
Combine filters with Make.com's Router module to send different messages to different Slack channels based on record type — for example, new leads go to #sales, new bugs go to #engineering.
Advanced: Use a Slack Webhook for Richer Messages
Make.com also supports posting to Slack via Incoming Webhooks, which unlocks Block Kit — Slack's rich message format with buttons, dividers, images, and more.
To use this:
Go to api.slack.com/apps and create a new app
Enable Incoming Webhooks and copy the webhook URL for your channel
In Make.com, use the HTTP module instead of the Slack module
POST your JSON payload to the webhook URL
Block Kit messages can look like structured cards with labeled sections — far more readable than plain text for complex records.
How Much Does This Cost?
For most small teams, the answer is: almost nothing.
Make.com's free plan includes 1,000 operations per month. Each scenario run uses one operation per module — so this two-module scenario (Airtable + Slack) uses 2 operations per poll cycle where records are found.
At 15-minute polling with 10 records per check, you'd use roughly 2,880 polling operations per month — but only a fraction of those will actually find changed records. In practice, most teams stay comfortably within the free tier.
If you need more, Make.com's Core plan starts at $9/month for 10,000 operations.
Airtable's free plan supports unlimited bases with up to 1,000 records per base — enough for most small teams.
Make.com vs. Zapier for This Integration
Both tools can connect Airtable to Slack, but there are meaningful differences:
Make.com offers a more visual scenario builder, better data transformation tools (you can manipulate field values mid-flow without writing code), and more generous pricing. The free tier is genuinely usable.
Zapier is simpler to set up for basic triggers (fewer clicks for a basic two-step Zap), and its ecosystem has more pre-built templates. But Zapier's free plan limits you to 5 Zaps and 100 tasks/month — you'll hit that ceiling quickly.
For teams that want to build more complex automations over time — adding conditions, multiple paths, data transformations — Make.com is the better long-term choice.
What to Build Next
Once your Airtable-to-Slack integration is running, you've got the building blocks for much more:
Daily summary: Instead of per-record notifications, aggregate all changes from the past 24 hours and send one morning briefing to Slack
Two-way sync: Use Slack's slash commands to update Airtable records directly from Slack (requires a more advanced scenario)
Escalation alerts: If a record stays in "Blocked" status for more than 24 hours, trigger a DM to the project owner
Cross-tool notifications: Extend the same pattern to notify in Microsoft Teams, Discord, or email — Make.com connects to hundreds of apps
The automation you built today is a template. Swap Airtable for any other data source (Google Sheets, HubSpot, a form tool), swap Slack for any other destination, and the pattern is the same.
Final Thoughts
Connecting Airtable to Slack with Make.com takes about 20 minutes to set up and saves your team hours of manual status checking every week. It's one of the highest-ROI automations you can build for a collaborative team — the kind that pays for itself the first day it runs.
The free tier covers most use cases. There's no reason to keep copy-pasting updates into Slack by hand.