> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/triggers.md).

# Airtable Triggers

Blocks for triggering workflows based on Airtable events like record creation, updates, and deletions.

## Airtable Webhook Trigger

### What it is

Starts a flow whenever Airtable emits a webhook event

### How it works

This block subscribes to Airtable webhook events for a specific base and table. When records are created, updated, or deleted, Airtable sends a webhook notification that triggers your workflow.

You specify which events to listen for using the event selector. The webhook payload includes details about the changed records and the type of change that occurred.

### Inputs

| Input               | Description                   | Type                  | Required |
| ------------------- | ----------------------------- | --------------------- | -------- |
| base\_id            | Airtable base ID              | str                   | Yes      |
| table\_id\_or\_name | Airtable table ID or name     | str                   | Yes      |
| events              | Airtable webhook event filter | AirtableEventSelector | Yes      |

### Outputs

| Output  | Description                           | Type           |
| ------- | ------------------------------------- | -------------- |
| error   | Error message if the operation failed | str            |
| payload | Airtable webhook payload              | WebhookPayload |

### Possible use case

**Real-Time Sync**: Automatically sync Airtable changes to other systems like CRMs or databases.

**Notification Workflows**: Send alerts when specific records are created or modified in Airtable.

**Automated Processing**: Trigger document generation or emails when new entries are added to a table.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/triggers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.