In short
Airtable connects to OmniChannels.ai through its own automations, not a marketplace extension. A Run a script action uses fetch to call our REST API with your Bearer token and send WhatsApp or SMS when a record changes. A When webhook received trigger can log delivery statuses back to the base. Make, Zapier or n8n can do the same without scripting.
What you can do
Send a WhatsApp template when a new row is added
When a record is created in a table, send an approved WhatsApp template with its field values, to contacts who have opted in.
Confirm a booking when its status changes
When a record's status changes to Confirmed, send an SMS or WhatsApp confirmation to the number in the record.
Alert the team when a delivery fails
Delivery statuses update the matching record; a second automation notifies the record's owner when the status is FAILED or REJECTED, instead of resending.
Keep a message log in the base
Write each returned message ID into the record, then update its status as SENT, DELIVERED and READ events arrive.
Send without scripting
Use a Make, Zapier or n8n workflow that watches the base and calls the API, when you prefer not to maintain a script.
How it connects
Add a Run a script action to an Airtable automation, pass in the record's fields as input variables, and use fetch to POST to the channel's send path on https://api.broadnet.me with an Authorization header holding Bearer and your token. Single SMS takes a JSON body, which suits a script; bulk and most other channel sends take multipart form data and are simpler through an automation tool or your own code. Anyone who can edit the automation can read the script, so limit edit access or keep the token in an automation tool's credential store instead.
To bring statuses back, add a When webhook received trigger, send its URL to our team or your account admin to configure as the webhook on your account, and update the matching record by message ID. Scripting actions and webhook triggers are available only on some Airtable plans, and webhook triggers have their own rate limits; check Airtable's current plan details.
- Send: Run a script action with fetch to https://api.broadnet.me
- Authentication: Authorization: Bearer <token> in the request
- Receive: When webhook received trigger URL configured on your account
- No-code alternative: Make, Zapier or n8n between Airtable and the API
- Never resend automatically from a status automation
Set it up
- 1
Request API access
Request test access and receive an API token. Test sends go only to your own verified numbers.
Guide: Quickstart: send your first message - 2
Create the automation trigger
Add an automation that runs when a record is created or matches conditions, such as a status field set to Confirmed.
- 3
Add a Run a script action
Pass the phone number and message fields in as input variables and POST them with fetch to the channel's send URL, with the Authorization header.
Guide: SMS API - 4
Store the message ID
Write the returned message ID back to the record, so status events can be matched to it later.
- 5
Receive delivery statuses
Create a second automation with a When webhook received trigger and send its URL to our team or your account admin, then test with your own number.
Guide: Webhooks and delivery statuses
Vendor documentation
Airtable is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Airtable; this page describes a connection built with Airtable's own MCP, HTTP or webhook features.
