Some people see a text long before they open an email, such as a plumber who is out on a job when a booking lands, or the customer who made that booking and wants to know it arrived. If the bookings live in Airtable, this guide shows how to send that text automatically. Thrum builds it from Airtable's "A record is added" and its built-in Text step on the client's own Twilio account, and two other routes are covered first.
Zapier with Twilio
Zapier pairs the two directly. Its Airtable and Twilio page lists templates including "Send SMS messages via Twilio for new Airtable records" and "Send Twilio SMS messages with new Airtable records in view", built on Twilio's action that sends an SMS to one or more numbers. The Airtable "New Record" event covers new records and records the first time they enter a chosen view, and Zapier's Free plan checks for new data every 15 minutes.
A script in Airtable
Airtable's automations have no general action for calling another service. Airtable's help centre sends you to "Run a script" for that, with fetch() inside the script and the key kept in Secrets. A run can make up to 50 fetch requests and each one times out after 30 seconds. Writing the request itself is up to you, and Twilio may also publish other approaches, so Twilio's documentation is the place to start.
Whatever sends the text, Airtable's notes about "When record created" are worth knowing. It only acts on records created after the automation is on, and a record someone is typing by hand will likely set it off before they finish. Airtable suggests "When record matches conditions" or "When record enters view" for hand-entered rows.
Building it in Thrum
This pair has no starter in the library, so you build the workflow on the canvas from two steps.
Start a workflow for the client. Create a new workflow in the client's workspace and choose Airtable's "A record is added" as the step that starts it.
Point it at the table. Fill in the Base ID (the appXXXXXXXXXXXXXX code) and the table's name, then choose the client's Airtable token. Make the token at airtable.com/create/tokens with data.records:read and data.records:write and give it the client's base.
Add the Text step. From the add-step menu, under Send, add the Text step. Leave "Send" on the Twilio option and pick the client's Twilio account under "Send with". That account needs three things from the Twilio console, the Account SID, the auth token and the number to send from, so the text arrives from the client's own number.
Fill in To and Message. For a text to the customer, set To to the phone column of the new row (
{{ trigger.payload.fields.Phone }}for a column called Phone). For an alert to the owner, type the owner's mobile number instead. Write the message with the columns it should mention, for example the customer's first name and the time they asked for.

- Publish and switch it on. The canvas now shows the Airtable step joined to the Text step. Thrum reads the table every 15 minutes and sends one text per row added since the previous read, oldest first. Rows that were there before the workflow went live are not texted.

Texting when a row reaches a stage
To text when a job is confirmed rather than when it is first entered, use "A record is changed" as the starting step. The table needs a field of the type "Last modified time", ideally limited to the columns that matter, and you give its name in the step. Add a view name as well, for example Ready to quote, and the workflow only acts on rows in that view, which reads as "a record enters Ready to quote".
When there is no number
Some rows arrive without a phone number. The Text step does not fail in that case. It sends nothing, the run carries on with any later steps, and the run's timeline says "Sent nothing" with the step's name and the place it looked for the number. You can see at a glance which bookings need a number added by hand.
When Twilio refuses or is slow
A server error or a request to slow down from Twilio is tried again, first after 5 seconds and then at doubling waits, up to 3 attempts. A refusal of any other kind fails the step at once, because sending the same request again would get the same answer. If the connection drops after Twilio has the request, Thrum leaves the retry to you so the customer is not texted twice.
Which route fits
Zapier covers the pair with ready templates on a Zapier account. A script keeps everything inside Airtable but needs someone to write and look after the code. Thrum suits the agency or freelancer who runs this kind of alert for many clients, each texting from their own Twilio number, with every send and skipped send visible in the run history. The Airtable and Twilio page shows both Airtable starting steps with the Text step.
Checked on 14 November 2026.
Sources



