Skip to content

Guide5 min read

Slack messages for new Airtable records

How to send a Slack message when an Airtable record is created

On this page

Your client's team lives in Slack and their work lives in Airtable, and they want a post in #leads each time the base gains a row. Airtable can do some of this by itself, Zapier can do it through its templates, and Thrum has a starter that posts with the client's own Slack app. This guide walks through all of them and ends with the Thrum setup in full.

Inside Airtable, two options

Base activity notifications. Airtable has a Slack feature that is separate from automations. From the menu beside a base's name you choose Slack notifications, then pick the base and the channel the updates go to. You can add as many of these rules as you need, so one base can post to #recruiting and another to #dev. Airtable lists its limits plainly. A record that enters a view because of a time-based filter sends no notification, and in a view, changes to hidden fields are ignored.

The "Slack: Send a message" action. In an automation, you add Slack from the actions menu (it sits under Integrations) and connect a Slack account. A fixed recipient is a single channel or user. The message can be fixed text, values from the record, or a mix, with Markdown for formatting, @mentions and a link back to the record. Posts show as coming from Airtable with its logo unless you change the bot's name and picture. Airtable asks for one successful test before the automation can be turned on, and a test with "Run as configured" posts for real (warn the channel first). There is also "Slack: Send an actionable message", which adds buttons that update the record and expires after 7 days without activity.

One detail from Airtable's notes about the "When record created" event applies to both. A row typed in by hand will likely set the automation off before the person has finished, so Airtable recommends "When record matches conditions" or "When record enters view" for rows people enter themselves.

Zapier

Zapier's Airtable and Slack page offers templates such as "Post new Airtable records to Slack" and "Post notifications about new Airtable records in a view to Slack". Its Airtable "New Record" event covers new records, and existing ones the first time they enter a chosen view. Zapier checks for new data every 15 minutes on its Free plan.

The Thrum starter, step by step

Thrum keeps each client in a separate workspace with their own keys, stored encrypted, so the post comes from an app in the client's Slack and the base is read with the client's Airtable token.

  1. Pick it from the library. Under Templates → Library, open "Post a message in Slack when a record is added in Airtable" and install it into the client. It lands switched off, with a checklist.
  1. Make the client's Slack app. In the client's Slack, go to api.slack.com/apps (the page where Slack apps are made), create a new app, add the chat:write scope under OAuth & Permissions, install it to the workspace and copy the Bot User OAuth Token. Then invite the app to the channel it will post in. Until it is invited, Slack turns the post away.

  2. Make the Airtable token. At airtable.com/create/tokens, give a new token the scopes data.records:read and data.records:write and add the client's base.

  3. Fill in the three fields. "Slack: Channel" takes a name like #leads or an ID like C0123456789. "Airtable: Base ID" is the appXXXXXXXXXXXXXX code, and "Airtable: Table" is the table's name.

The checklist for an example client with both accounts connected and the channel, base ID and table filled in.
  1. Write the post. The installed text is two lines, "A record is added in Airtable." and "Added at:" followed by the time Airtable created the row. That tells the team something happened without saying what. Open the Slack step and add the columns they look at first (each column by name, such as {{ trigger.payload.fields.Customer }} for a Customer column).
The workflow on the canvas after installing, with the Airtable step for new records leading to the Slack post.
  1. Turn it on. Thrum looks at the table every 15 minutes and posts once for each row added since its last look, oldest first. Rows that were in the table before you switched it on stay quiet.

How Thrum treats a bad Slack token

Slack can answer a revoked token with a success code and an error tucked inside the reply. Thrum reads the reply, so a dead token fails the step and shows up on the client's health, where a plain status check would have logged the post as sent. Busy and server errors are tried again at growing waits, up to 3 attempts. A post whose connection dropped mid-request is not repeated automatically, so the channel never gets a double post without you choosing to retry.

Other ways the two join in Thrum

The same pair can post when a row is changed rather than added. That version asks for a "Last modified time" field in the table and can be limited to one view, such as Ready to quote. In the other direction, each new message in a Slack channel can become an Airtable row, checked every 5 minutes. The Slack side also has "Edit a message", which updates the bot's post in place, for example one line per lead that moves from new to booked. The Airtable and Slack page lists all the combinations with their starters.

Choosing between them

If the client wants a feed of edits to a base, Airtable's notification rules cover it with no automation. For one custom message on one base, Airtable's automation action is close at hand. Thrum earns its place when you run the same alert for many clients and want each one on the client's own accounts, with retries and an alert when a key stops working.

Checked on 14 November 2026.

Sources

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.