Skip to content
Nappai Documentation

Airtable Webhook

The Airtable Webhook component lets your Nappai dashboard listen for incoming webhook calls from Airtable. When a record is created, updated, or deleted in Airtable, Airtable can send a JSON payload to this component, which then makes the data available for the rest of your workflow.

How it Works

When you add the Airtable Webhook component to a flow, it opens a public URL that Airtable can call. Each time Airtable sends a request, the component parses the JSON payload, optionally stores the record as a message in the conversation history, and then outputs two pieces of information:

  1. Message – a structured message that can be used by other components that expect a conversation‑style input.
  2. Data – the raw JSON data from Airtable, ready to be passed to downstream components such as data processors or AI models.

No external API calls are made by the component itself; it simply receives and forwards the data.

Inputs

Before you can use the component, you must set up an Airtable API credential in Nappai’s credential manager.

  1. Go to Credentials → Add Credential → choose Airtable API.
  2. Enter your Airtable Access Token (found in your Airtable account under Account).
  3. In the Airtable Webhook component, select this credential in the Credential field.

Input Fields

The following fields are available to configure this component.

  • Data: Use this field to quickly test the webhook component by providing a JSON payload.
  • Store Record as Message: Store incoming Airtable records in the conversation history.

Outputs

  • Message – A Message object created from the incoming Airtable record.
  • Data – The raw JSON data received from Airtable, ready for further processing.

Usage Example

  1. Add the Airtable Webhook component to your flow.
  2. Configure the credential as described above.
  3. Enable “Store Record as Message” if you want the record to appear in the conversation history.
  4. Connect the “Data” output to a downstream component, such as a Text Analyzer or a Database Writer, to act on the record.
  5. In Airtable, set up an automation that triggers on record creation or update and points its webhook URL to the one provided by the component.

Now, whenever a record changes in Airtable, the webhook fires, the component receives the data, and your workflow can react automatically.

  • Airtable Query – Retrieve records from Airtable based on filters.
  • Webhook Trigger – Send data from Nappai to external services via HTTP.
  • Data Formatter – Transform JSON data into different formats for downstream use.

Tips and Best Practices

  • Use the Data input to test the component with sample JSON before connecting it to Airtable.
  • Keep the Airtable API credential in a secure location; never expose the access token in public flows.
  • If you only need the raw data, disable Store Record as Message to reduce clutter in the conversation history.
  • Combine this component with a Data Formatter to clean or reshape the payload before passing it to AI models.

Security Considerations

The component relies on an Airtable API key to authenticate webhook calls. Store this key in Nappai’s credential manager and avoid sharing it in public or shared flows. Ensure that only trusted users have access to the credential and that the webhook URL is not exposed to the public internet unless necessary.