Airtable Webhook
Airtable Webhook receives in your flow the notifications Airtable sends when a record in a base is created or changed. Every time a notification arrives, the flow runs and receives the full notification and, separately, the fields of the record as text.
It is the starting point of flows that must react to what happens in your Airtable tables, without anyone having to start them by hand.
When to use it
- Alert the sales team every time a lead is added to a table.
- Have an agent draft a reply when a new request comes in through an Airtable form.
- Log in another tool the status changes of the orders you manage in Airtable.
Configuration
| Field | What it does |
|---|---|
| Credential | The Airtable API credential of your account. See Credentials. |
| Data | Used to test the flow in the editor: paste an example of the data Airtable sends. When the flow runs through its webhook, this field is filled with the data received. |
| Access Token | The access token of your Airtable base. Airtable’s notifications only say that the base changed: with the token, the component reads the change itself. Not needed when what arrives already carries the record. |
Advanced options
| Field | What it does |
|---|---|
| Store Record as Message | Saves each record received in the conversation history. On by default. |
Getting the webhook address
- Deploy a version of the flow: notifications run the deployed version. See Versions and publishing.
- Open the API Access window and go to the Webhook tab.
- Pick the API Key the call will use and copy the address. See API keys.
- In Airtable, set up the changes of your base to be sent to that address.
Output
| Output | What it returns |
|---|---|
| Message | The fields of the record created or changed, as text, identified as Airtable identifies them (by field ID). If the notification carries several records, it returns the first one. Each record is treated as its own conversation. Connect it to an agent. |
| Data | All the data in the notification, as Airtable sends it. If what arrives is not valid data, it comes through as is, as a single text. |
Example
An agency collects the quote requests from its website in Airtable:
- Add Airtable Webhook and paste a sample notification into Data to build the flow.
- Connect Message to an agent that summarises the request and suggests the next steps.
- Email the summary to the sales manager.
- Deploy the flow and, in Airtable, set up new records to be sent to the address in the Webhook tab.
Good practices
- A flow can only have one webhook component.
- Don’t share the webhook address: it includes the API key, and anyone who has it can run the flow.
Related components
- Webhook Input: receives data from any other application.
- Parse Data: turns the data received into text.