Integration · Automate and collaborate
Airtable and Meteor AI agents
Connect Airtable to a WhatsApp Met: search records, create and update rows in your tables and draft automations through the official MCP server.
How does Airtable connect to Meteor?
With the Airtable ready connector, your WhatsApp Met works on your company's bases with the account the admin authorizes. It finds the base and the table, reads their structure, searches for a record by keyword and answers with that value: a product's stock, an order's status or a customer's record. If you turn it on, it also creates records, 10 per request, and updates only the fields you ask for. It is Airtable's official server, available on every Airtable plan; usage counts against your account's limits, and delete actions start switched off.
What it automates
What a Meteor Met does with Airtable
Answer with the value that lives in your base
When a customer asks about a product or their order, your Met searches the matching table for the record and answers with the value Airtable holds at that moment: stock, price, status or date.
Log what arrives on WhatsApp in a table
If you turn it on, the Met creates a record with the person's request in the table your team already uses, following its existing fields. Each request creates up to 10 records.
Update only the field that changed
When the customer confirms an address or changes the quantity, the Met updates that field on the record and leaves the others alone, so the rest of the row stays as your team left it.
Undo a change that went wrong
If an update ended up with a wrong value and Airtable allows reverting it, the Met can undo it with that action's ID, without deleting the record.
40 tools
Everything your Met can ask Airtable for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
create_automation | Creates a draft automation; it stays off until you turn it on in Airtable. |
delete_automation | Deletes an automation that is turned off. It is destructive and starts switched off. |
fetch_automation_input_data | Fetches the dynamic options of a trigger or action for an external account. |
get_automation | Returns an automation's full configuration and its status. |
get_create_automation_instructions | Returns the specification for building or updating automations. |
list_automations | Lists the automations in a base with their status and trigger. |
test_automation_webhook_trigger | Tests a webhook trigger again to capture the format of the latest request. |
update_automation | Replaces the draft configuration of an automation. |
create_base | Creates a new base in a workspace where the account has creator permission. |
list_bases | Lists the bases the connected account can access. |
search_bases | Searches bases by name and recommends the best match. |
create_field | Adds a field to an existing table. |
update_field | Changes a field's name, description or formula, not its type. |
get_form_schema | Returns a form's sections, fields and conditions. |
submit_form | Submits a response to an Airtable form. |
create_interface | Creates an interface in a base so the team can work without opening the tables. |
create_page | Creates an interface page of the visualization, dashboard or record detail type. |
delete_interface | Deletes an interface with all its pages. It starts switched off. |
delete_page | Deletes a page from an interface. It starts switched off. |
list_records_for_page | Lists the records on an interface page, even with interface-only access. |
get_record_for_page | Gets one record from an interface page, even with interface-only access. |
describe_page_element | Returns the configuration options of a page element, such as a list or a chart. |
describe_page_type | Returns the configuration options of an interface page type. |
list_pages_for_base | Lists the interfaces in a base and their pages. |
create_records_for_table | Creates records in a table, up to 10 per request. |
delete_records_for_table | Deletes records by ID. It is destructive and starts switched off. |
display_records_for_table | Shows records in an interactive board or levels view meant for other clients. |
list_records_for_table | Lists a table's records with optional filters and sorting. |
revert_action | Undoes an eligible earlier change, using the action's ID. |
search_candidate_linked_records | Searches candidate records for a field that links to another table. |
search_records | Searches a table's records by keyword. |
update_records_for_table | Updates the given fields on existing records and leaves the rest unchanged. |
create_table | Creates a table in a base. |
delete_table | Deletes a table with its records, fields and views. It starts switched off. |
get_table_schema | Returns a table's fields with their name, ID, type and configuration. |
list_views_for_table | Lists a table's views with their ID, name and type. |
list_tables_for_base | Lists the structure of every table in a base. |
update_table | Changes a table's name or description. |
list_workspaces | Lists the Airtable workspaces the account can access. |
list_external_accounts | Lists the third-party accounts connected to Airtable, such as Slack or Google. |
The limits
What the Airtable integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not ask for confirmation in the chat before writing to Airtable. The admin chooses in Connections which actions stay on; delete actions start switched off.
-
It sees no more than the account that authorized the connection. With read-only or commenter access it only reads, and development bases answer with a 403 error.
-
It does not turn automations on. It creates and edits them as drafts, but activating them happens in Airtable, and automations with script actions cannot be created or edited through the connector.
-
It does not edit existing interfaces or add filters to them: it can create a new one, but changes to an existing interface happen in Airtable's interface designer.
-
It does not change a field's type or its select options. That still happens on the Airtable screen.
-
Usage runs on your Airtable account: there is no separate charge, but the standard API limits apply and the records created count against your base's limit.
Before you start
What you need to connect Airtable
- 1
An Airtable account with access to the bases
Any Airtable plan works. The account you connect needs access to the base, not only to an interface, to read and write in the tables. On Enterprise accounts an administrator may need to allow the integration.
- 2
Connect it in Met
In Met, open Connections → Airtable → Connect. An Airtable window opens so you can sign in and authorize Met. Then you choose which actions stay on.
Frequently asked questions
Questions about Airtable and Meteor
It should not: before writing it can read the table's structure with its fields and types, and Airtable rejects a change to a field the account is not allowed to modify.
Up to 10 per request, which is the cap of Airtable's official server. For large loads, the Airtable import is a better fit than a conversation.
Only if the admin turns that action on, because it starts switched off. The same applies to deleting tables, interfaces, pages and automations.
No. The MCP server is available on every Airtable plan with no separate charge. What does apply are your plan's limits, such as the number of records per base.
Step by step
Automations that use Airtable
Complete tasks, with the steps and the tools that run at each one.
Automate and collaborate
Other integrations in the same family
Want to see a Met running Airtable?
We will show you with your own account connected, not with a canned demo.