Beginner~12 min setupProductivity & CommunicationVerified April 2026
Airtable logo
Slack logo

How to Send Status Change Alerts to Slack with Make

Automatically send Slack DMs to assigned team members when Airtable record status changes.

Steps and UI details are based on platform versions at time of writing β€” check each platform for the latest interface.

Best for

Teams that need instant notifications when project statuses change in Airtable

Not ideal for

Teams that prefer digest-style notifications or don't use status-based workflows

Sync type

real-time

Use case type

notification

Real-World Example

πŸ’‘

A 12-person marketing agency tracks campaign projects in Airtable with statuses like Draft, Review, Approved, Live. When a designer moves a campaign from Draft to Review, the assigned project manager gets a Slack DM instantly. Before automation, status changes sat unnoticed for hours because team members checked Airtable sporadically.

What Will This Cost?

Drag the slider to your expected monthly volume.

/mo
505005K50K

Each platform counts differently β€” Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.

Prices shown for annual billing. Based on published pricing as of April 2026.

Estimated ROI

1000

min saved/mo

$583

labor value/mo

Free

no platform cost

Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.

Implementation

Skip the setup

Import this workflow directly into Make

Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured β€” you just need to connect your accounts.

Before You Start

Make sure you have everything ready.

Creator or Owner access to the Airtable base with webhook permissions
Slack workspace admin approval to install Make integration app
Airtable API key with read access to your base
Assigned team member field containing Slack usernames or email addresses

Optional

Status field in Airtable with consistent text values (not single-select)

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Record Name
Status
Assigned To
Record URL
3 optional fieldsβ–Έ show
Due Date
Project Type
Priority

Step-by-Step Setup

1

Airtable Base > Help > API Documentation

Enable Airtable webhooks

In your Airtable base, go to the API documentation page and scroll to the webhooks section. Copy your base ID from the URL - it starts with 'app'. You'll need Creator or Owner permissions to set up webhooks. Airtable webhooks fire within 1-2 seconds of record changes.

  1. 1Click Help in your Airtable base header
  2. 2Select 'API Documentation' from the dropdown
  3. 3Copy the Base ID from the intro section
  4. 4Note your table name (case sensitive)
βœ“ What you should see: You should see your base ID starting with 'app' and table structure displayed in the API docs.
⚠
Common mistake β€” Webhooks only work with Creator or Owner permissions - Commenter and Editor roles cannot create them.
2

Make Dashboard > Scenarios > Create Scenario

Create new Make scenario

Log into Make and create a new scenario. The free tier gives you 1,000 operations per month which covers about 500 status changes (each change uses 2 operations - webhook receive + Slack send). Choose Airtable as your first module and select 'Watch Records' as the trigger.

  1. 1Click the + Create a new scenario button
  2. 2Search for 'Airtable' in the apps list
  3. 3Select 'Watch Records (instant)' trigger
  4. 4Click 'Create a webhook' in the webhook field
βœ“ What you should see: You should see an Airtable module with a webhook URL starting with hook.integromat.com.
3

External API Tool > POST Request

Configure Airtable webhook

Copy the webhook URL from Make and return to Airtable. Register the webhook using Airtable's API or a tool like Postman. The webhook needs to listen for field changes on your status column specifically. Set the specification to only fire when your status field changes to reduce unnecessary triggers.

  1. 1Copy the webhook URL from your Make module
  2. 2Use curl or Postman to POST to https://api.airtable.com/v0/bases/YOUR_BASE_ID/webhooks
  3. 3Include your API key in Authorization header
  4. 4Set notificationUrl to your Make webhook URL
  5. 5Add specification filters for your status field only
βœ“ What you should see: You should receive a webhook ID and see 'enableNotifications: true' in the response.
⚠
Common mistake β€” Webhook registration expires after 7 days of inactivity - you'll need to refresh it if testing gaps occur.
4

Airtable Base > Your Table > Status Field

Test webhook connection

Go back to your Airtable base and change a record's status field. Within 30 seconds, you should see data appear in Make's webhook module. If nothing appears, check your webhook registration and ensure the API key has the correct base permissions.

  1. 1Open any record in your Airtable base
  2. 2Change the status field to a different value
  3. 3Return to Make and check the webhook module
  4. 4Click 'Run once' if the scenario isn't running
βœ“ What you should see: The Airtable module should show a green success badge with sample data from your changed record.
⚠
Common mistake β€” Copy the webhook URL carefully β€” it expires if you regenerate it, and any scenarios using the old URL will silently stop working.
Make
β–Ά Run once
executed
βœ“
Airtable
βœ“
Slack
Slack
πŸ”” notification
received
5

Make Scenario > Add Module > Router

Add conditional logic

Add a router after the Airtable module to handle different status changes. Create filters for each status you want to trigger alerts - like 'Status equals Review' or 'Status equals Approved'. This prevents alerts for every minor field change and focuses on meaningful status transitions.

  1. 1Click the + icon after your Airtable module
  2. 2Search for 'Router' and select it
  3. 3Add a route and set up a filter condition
  4. 4Choose 'Status' field and set condition to 'Equal to'
  5. 5Enter the status value that should trigger alerts
βœ“ What you should see: You should see a router with filtered routes showing your status conditions.
⚠
Common mistake β€” Use exact text matches - 'In Review' and 'in review' are different values that won't match.
Airtable
AI
trigger
filter
Condition
matches criteria?
yes β€” passes through
no β€” skipped
Slack
SL
notified
6

Make Router Route > Add Module > Slack

Connect Slack workspace

Add a Slack module after your router route. Choose 'Create a Direct Message' action since you want to notify specific team members. You'll need to authorize Make to access your Slack workspace with the necessary permissions to send DMs and read user information.

  1. 1Click + after your router route
  2. 2Search for 'Slack' and select it
  3. 3Choose 'Create a Direct Message' action
  4. 4Click 'Add' to connect your Slack account
  5. 5Authorize the requested permissions
βœ“ What you should see: You should see 'Connection verified' and the Slack module should show configuration options.
⚠
Common mistake β€” Make needs 'chat:write' and 'users:read' scopes - if your workspace restricts app installations, ask your Slack admin first.
Make settings
Connection
Choose a connection…Add
click Add
Airtable
Log in to authorize
Authorize Make
popup window
βœ“
Connected
green checkmark
7

Slack Module > Configuration > To Field

Map recipient field

In the Slack module, you need to specify who receives the DM. If your Airtable has an 'Assigned To' field with Slack usernames or emails, map that field to the 'To' parameter. For email addresses, Make will automatically look up the corresponding Slack user ID.

  1. 1Click in the 'To' field of the Slack module
  2. 2Select your assigned user field from Airtable data
  3. 3Choose 'User by name' if using Slack display names
  4. 4Choose 'User by email' if your Airtable stores email addresses
βœ“ What you should see: The 'To' field should show the mapped Airtable field name in curly braces.
Airtable fields
Name
Email
Status
Notes
Created
available as variables:
1.props.Name
1.props.Email
1.props.Status
1.props.Notes
1.props.Created
8

Slack Module > Message Field

Compose message content

Create a message template that includes relevant context. Reference the record name, old status, new status, and a link back to Airtable. Use Make's text functions to create a professional notification that gives the recipient everything they need to take action.

  1. 1Click in the 'Text' field of the Slack module
  2. 2Type your message template with placeholders
  3. 3Map Airtable fields like record name and status
  4. 4Add the Airtable record URL for quick access
  5. 5Include context about what changed
βœ“ What you should see: Your message should show mapped field names in curly braces within your text template.
⚠
Common mistake β€” Airtable record URLs need the base ID and record ID - don't hardcode the base URL as it varies by workspace.
Message template
πŸ“¬ New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
9

Make Scenario > Run Once

Test complete workflow

Run the complete scenario by changing another record's status in Airtable. The assigned team member should receive a Slack DM within 10-15 seconds. Check that the message content looks correct and the Airtable link works. Test with different status values to ensure your routing works properly.

  1. 1Click 'Run once' in Make
  2. 2Switch to Airtable and change a record's status
  3. 3Check the assigned person's Slack DMs
  4. 4Verify the message content and Airtable link
  5. 5Test with multiple status changes
βœ“ What you should see: You should see successful execution bubbles on all modules and receive the Slack DM as expected.
10

Make Scenario > Scheduling Toggle

Enable automatic execution

Turn on the scenario to run automatically. Set it to run continuously rather than on a schedule since you're using webhooks for instant triggers. Monitor the first few executions to ensure everything works smoothly, then let it run in the background.

  1. 1Click the scheduling toggle to 'ON'
  2. 2Select 'Immediately as data arrives'
  3. 3Click 'OK' to confirm the scheduling
  4. 4Monitor the execution history for any errors
βœ“ What you should see: The scenario status should show 'Active' with a green indicator.
⚠
Common mistake β€” Webhook-based scenarios don't respect the scheduling interval - they fire immediately when triggered regardless of timing settings.

This formula creates dynamic messages based on priority level and includes time-sensitive formatting. Paste it into the Slack message text field to replace static text.

JavaScript β€” Custom Functionif(
β–Έ Show code
if(
  {{airtable.priority}} = "High";
  "🚨 URGENT: " + {{airtable.name}} + " status changed to " + {{airtable.status}} + "\n" +

... expand to see full code

if(
  {{airtable.priority}} = "High";
  "🚨 URGENT: " + {{airtable.name}} + " status changed to " + {{airtable.status}} + "\n" +
  "Priority: " + {{airtable.priority}} + "\n" +
  "Due: " + formatDate({{airtable.due_date}}; "MM/DD/YYYY") + "\n" +
  "View record: " + "https://airtable.com/" + {{airtable.base_id}} + "/" + {{airtable.record_id}};
  
  if(
    {{airtable.priority}} = "Medium";
    "πŸ“‹ " + {{airtable.name}} + " moved to " + {{airtable.status}} + "\n" +
    "Priority: " + {{airtable.priority}} + "\n" +
    "View: " + "https://airtable.com/" + {{airtable.base_id}} + "/" + {{airtable.record_id}};
    
    "βœ… Status update: " + {{airtable.name}} + " β†’ " + {{airtable.status}} + "\n" +
    "View: " + "https://airtable.com/" + {{airtable.base_id}} + "/" + {{airtable.record_id}}
  )
)

Going live

Production Checklist

Before you turn this on for real, confirm each item.

Troubleshooting

Common errors and how to fix them.

Frequently Asked Questions

Common questions about this workflow.

Analysis

VerdictWhy Make for this workflow

Use Make for this if your team needs instant status notifications and wants visual scenario building. Make's webhook handling is rock-solid - I've seen scenarios run for months without missing a single Airtable change. The router system makes it easy to create different message types for different statuses. Skip Make if you need complex Slack formatting or thread management - Zapier handles Slack's advanced features better.

Cost

Real math: each status change burns 2 operations (webhook receive + Slack send). At 300 status changes per month, you're looking at 600 operations total. Make's free tier covers 1,000 operations monthly, so you're safe until about 500 changes per month. That's when you'll hit the $9/month Pro plan. Zapier's free tier only covers 100 tasks, so Make wins on volume.

Tradeoffs

Zapier handles Slack better with built-in message formatting and thread support that Make lacks. n8n gives you more control over webhook payload processing if you need complex data transformations. Power Automate integrates tighter with Microsoft teams using the same base pattern. Pipedream offers better error handling and retry logic out of the box. But Make's visual builder makes this workflow easier to troubleshoot when Airtable changes their webhook payload structure.

Things you'll hit: Airtable webhooks expire after 7 days of inactivity during testing, so refresh them if your scenario stops working. Slack user lookups fail silently if someone leaves the workspace - your scenario succeeds but no message sends. Make doesn't preserve webhook order under high load, so rapid status changes might arrive out of sequence. Field mapping breaks when Airtable renames columns because Make doesn't auto-update references.

Ideas for what to build next

  • β†’
    Add status change summaries β€” Create a daily digest that summarizes all status changes in a team channel instead of individual DMs.
  • β†’
    Set up reverse notifications β€” Alert record owners when someone comments or makes changes to their assigned items.
  • β†’
    Connect multiple bases β€” Expand the workflow to monitor status changes across different Airtable bases and route to appropriate Slack channels.

Related guides

Was this guide helpful?
← Airtable + Slack overviewMake profile β†’