How to set up webhooks with Airtable on Tenklo

Airtable webhooks are created per base through the Airtable API. A notification carries no record data, only the base and webhook ids, so fetch the changes with the list webhook payloads endpoint once you receive one.

How it worksCopy Anchor Link

1. Airtable sends a POST request to your Tenklo webhook URL when something changes in a base the webhook watches.
2. Tenklo finds the connection whose metadata holds the notification's webhook.id under webhooks.
3. Tenklo verifies the X-Airtable-Content-MAC header with the macSecretBase64 stored for that webhook, then routes the notification to the connection.

A notification whose webhook id does not match a connection, or whose connection has no macSecretBase64 stored for it, is rejected.

SetupCopy Anchor Link

1. Create the webhook and store its secretCopy Anchor Link

Create the webhook through Tenklo's proxy, using your Tenklo webhook URL from the integration's Webhooks section in the dashboard:

curl -X POST "https://api.tenklo.dev/proxy/v0/bases/<BASE-ID>/webhooks" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>" \
  -H "Content-Type: application/json" \
  -d '{
    "notificationUrl": "<NANGO-WEBHOOK-URL>",
    "specification": { "options": { "filters": { "dataTypes": ["tableData"] } } }
  }'

Airtable returns the webhook id and a macSecretBase64. The secret is only returned once, so store it in the connection's metadata right away as webhooks.<WEBHOOK-ID>, with the macSecretBase64 string as the value.

The create-webhook action template does both steps and keeps the webhooks already stored on the connection. Use it, or copy its approach in your own function.

If you store the secret through the API instead, send the full webhooks object:

curl -X PATCH "https://api.tenklo.dev/connections/metadata" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "connection_id": "<CONNECTION-ID>",
    "provider_config_key": "<INTEGRATION-ID>",
    "metadata": {
      "webhooks": {
        "<EXISTING-WEBHOOK-ID>": "<EXISTING-MAC-SECRET-BASE64>",
        "<WEBHOOK-ID>": "<MAC-SECRET-BASE64>"
      }
    }
  }'

Handle the webhookCopy Anchor Link

Once routed, you have two options:

• Forward it to your app: Nango forwards the notification to your webhook URL with connection attribution. See External webhook forwarding.
• Process it in a sync: run a sync when the webhook arrives using webhookSubscriptions and onWebhook in a sync script. See Real-time syncs.