Recipe
Webhook to Airtable: Log Events as Rows Without a Workflow Tool
"When this happens, add a row" is one of the most common reasons people sign up for a workflow platform. If the thing that happens can send a webhook, Airtable's own API is one request away, and a template is all the mapping you need.
17 November 2026 · 4 min read
What you will end up with
Every matching webhook becomes a record in a table, with the fields you chose in the columns you chose. Sign-ups, form submissions, orders, support escalations, deploys: anything a service will send you.
Step 1: get Airtable ready
- Create the table and its columns. For this example: Name, Email, Plan (single select), Seats (number), Source and Received (date with time).
- Create a personal access token in Airtable's developer hub with the
data.records:writescope, and give it access to this one base only. - Find the base ID. It is the part of the base's web address that starts with
app.
Step 2: capture the webhook
Create a webhook.stream URL, register it with the sending service and trigger one event. Suppose a sign-up arrives looking like this:
{
"event": "signup.created",
"user": {
"name": "Maya Okafor",
"email": "Maya@Example.com",
"plan": "team",
"seats": "5"
},
"utm": {
"source": "newsletter"
}
}Step 3: the automation
Select that request, open Automations and choose Custom request.
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://api.airtable.com/v0/appXXXXXXXXXXXXXX/Signups |
| Extra header | Authorization: Bearer pat… |
| Content type | application/json |
The last part of the URL is the table's name. If the name has spaces, use the table ID (it starts with tbl) instead.
{
"fields": {
"Name": "{{body.user.name}}",
"Email": "{{body.user.email | trim | lower}}",
"Plan": "{{body.user.plan | default: \"free\"}}",
"Seats": "{{body.user.seats | number}}",
"Source": "{{body.utm.source | default: \"direct\"}}",
"Received": "{{request.timestamp}}"
},
"typecast": true
}What each part is doing:
- Keys are your column names, spelled exactly as in Airtable.
| numberturns the text"5"into the number5, which a number column requires. If the sender already sends a number, a lone placeholder keeps it as one.| trim | lowernormalises the email so the same person does not appear twice with different capitalisation.defaultfills the gaps for sign-ups with no campaign.typecast: trueasks Airtable to convert values where it can, and to create a new single-select option if "team" does not exist yet.
Add a condition so only the right events become rows:
| Field | Operator | Value |
|---|---|---|
body.event | equals | signup.created |
Step 4: test and read the reply
Press Send test. On success Airtable answers 200 with the record it created. When it refuses, the delivery log shows the start of its reply, and Airtable's errors are specific:
| Airtable says | Fix |
|---|---|
UNKNOWN_FIELD_NAME | A key in fields does not match a column name exactly |
INVALID_VALUE_FOR_COLUMN | A type mismatch: add | number, or check the date format |
AUTHENTICATION_REQUIRED or 401 | The token is wrong or the Bearer prefix is missing |
403 | The token lacks the write scope or access to this base |
404 | The base ID or table name in the URL is wrong |
Things worth knowing
- One row per webhook. A template cannot loop, so a payload with a list of items becomes one record, not one per item. Store the list in a long-text column with
{{body.items | json}}if you need it. - Airtable's rate limit is five requests a second per base. A burst beyond that gets
429and those rows are logged as failed. For steady traffic this never comes up. - Deliveries are not retried and there is no de-duplication. If the sender delivers an event twice, you get two rows. Add the sender's event ID as a column so duplicates are easy to spot.
- The token is stored with the automation and readable by anyone with the dashboard link. Scope it to one base and do not share the link.
What about Google Sheets?
Sheets has no simple URL that accepts a row. The usual workaround, an Apps Script web app, answers every request with a redirect to another host. Automations do not follow redirects, so each delivery is logged as failed even when the script ran, and the automation pauses itself after 15 of those. For a spreadsheet-shaped destination, Airtable or any database with a REST endpoint is the better fit.
Variations
- Other tables and databases: anything that accepts a JSON record over HTTPS with a token header works the same way. Only the URL, the header and the outer shape of the template change.
- Keep the whole payload: add a long-text column and map it to
{{raw | truncate: 5000}}for later debugging. - Row and notification together: add a second automation on the same URL that posts to chat.
Map a real payload
Create a URL, send it the event you want to log, and build the field mapping against the request that arrives.
Keep reading
Transform a webhook payload
Reshape webhook JSON into the payload another API expects using a template: pick fields, keep types, set defaults and format values, with a live preview against a real request.
ReadA lighter alternative to Zapier for webhooks
If your automation is one step long (a webhook arrives, a request goes out), you do not need a workflow platform. What a lightweight webhook relay does, where it stops, and how to choose.
Read