| airtable_create_base_schemaA | Provisions multiple tables and custom fields in an Airtable base using the official Metadata API. Supports singleLineText, singleSelect, currency, number, formula, checkbox, multipleRecordLinks, and more. When to UseWhen initializing a new application, portal, or workflow with multiple relational tables. When creating tables with customized field types, select choices, or currency configurations. When establishing the core data schema before building Interface Designer pages.
When NOT to UseDo NOT use this tool to add a single field to an existing table. Use 'airtable_modify_schema' instead. Do NOT use this tool to insert records. Use 'airtable_batch_upsert' instead. Do NOT use this tool to inspect table field IDs. Use 'airtable_list_schema' instead.
Operational DisclosuresSide Effects: Creates permanent tables and field columns in the target Airtable base. Persistence: Irreversible via this tool; created tables must be deleted manually from the Airtable UI if abandoned. Rate Limits: Tables are created sequentially with 250ms spacing to prevent Metadata API 429 rate limit errors. Auth Scopes: Requires Personal Access Token with 'schema.bases:write' scope.
|
| airtable_list_schemaA | Retrieves the complete schema structure of an Airtable base (all tables, field names, field IDs, field types, select options, and views) via the Metadata API. When to UseWhen discovering existing table names, primary fields, or field types before performing queries or updates. When you need field IDs (starts with 'fld...') or table IDs (starts with 'tbl...') for interface or webhook configurations. When validating that newly provisioned tables and fields exist.
When NOT to UseOperational Disclosures |
| airtable_modify_schemaA | Evolves an existing Airtable schema: adds new custom fields to an existing table, updates field names/descriptions, or updates table names/descriptions via Metadata API. When to UseWhen adding a new column/field to an existing table without recreating the whole base. When renaming a field or table to improve operational clarity. When updating field or table documentation descriptions.
When NOT to UseDo NOT use this tool to initialize an entire new base schema with multiple tables. Use 'airtable_create_base_schema' instead. Do NOT use this tool to update row values or cell data. Use 'airtable_manage_records' instead.
Operational DisclosuresSide Effects: 'create_field' adds a persistent new column. 'update_field' and 'update_table' mutate existing schema metadata. Persistence: Schema modifications are immediately persistent across all base views and interfaces. Auth Scopes: Requires Personal Access Token with 'schema.bases:write' scope.
|
| airtable_batch_upsertA | Ingests or bulk-inserts records into an Airtable table using the REST API with automatic 10-record chunking and 5 req/sec rate limit backoff. When to UseWhen bulk-importing rows of data from CSVs, webhooks, or external systems into an Airtable table. When creating multiple records in batches of 10 to 1,000+ rows efficiently without manual loop management. When inserting structured data where string values for singleSelect or record links should be auto-cast.
When NOT to UseDo NOT use this tool to update or delete a single record by record ID. Use 'airtable_manage_records' instead. Do NOT use this tool for reading or filtering existing records. Use 'airtable_query_records' instead. Do NOT use this tool to create new tables or modify field schemas. Use 'airtable_create_base_schema' or 'airtable_modify_schema' instead.
Operational DisclosuresSide Effects: Creates new persistent records in the target table. Does not overwrite existing rows unless fields match Airtable's native upsert performUpsert criteria. Persistence & Idempotency: Additive mutation. Calling multiple times with identical records will create duplicate records unless an external primary key is deduplicated beforehand. Rate Limiting: Airtable enforces a strict 5 req/sec limit. This tool chunks records into 10-item payloads and sleeps 210ms between requests, with exponential backoff on HTTP 429. Auth Scopes: Requires Personal Access Token with 'data.records:write' scope.
|
| airtable_query_recordsA | Queries records from an Airtable table with server-side formula filtering, field selection, sorting, and pagination. When to UseWhen searching for specific records matching criteria (e.g. stage, status, date range, or email). When retrieving record IDs, computed formulas, or linked fields for downstream analysis or updates. When inspecting current data density and values across an Airtable base.
When NOT to UseDo NOT use this tool to modify or delete records. Use 'airtable_manage_records' or 'airtable_batch_upsert' instead. Do NOT use this tool to inspect table column schemas. Use 'airtable_list_schema' instead.
Operational DisclosuresSide Effects: Read-only. Safe to invoke repeatedly with zero mutations to the base. Filtering: Supports standard Airtable formula syntax (e.g. AND({Status} = 'Active', {Balance} > 0)). Pagination: Automatically paginates using Airtable offset tokens up to max_records. Auth Scopes: Requires Personal Access Token with 'data.records:read' scope.
|
| airtable_manage_recordsA | Performs lifecycle operations on individual or batch records in Airtable: get record by ID, update fields (PATCH), delete single record, or batch delete up to multiple records. When to UseWhen updating specific fields on an existing record (e.g. changing Stage from 'Review' to 'Approved'). When retrieving the full payload of a single record by known record ID (starts with 'rec'). When permanently deleting one or more records by their record IDs.
When NOT to UseDo NOT use this tool to insert dozens of new rows. Use 'airtable_batch_upsert' instead. Do NOT use this tool for formula-based search or multi-record filtering. Use 'airtable_query_records' instead. Do NOT use this tool to delete an entire table or change schema definitions. Use 'airtable_modify_schema' instead.
Operational DisclosuresDestructive Behavior: The 'delete' and 'batch_delete' actions permanently remove records from Airtable (moved to base trash for 7 days). Partial Updates: The 'update' action performs a PATCH: only specified fields are modified; unmentioned fields retain their existing values. Rate Limits: Single requests execute in 1 call; 'batch_delete' automatically chunks IDs by 10 and respects the 5 req/sec rate limit. Auth Scopes: Requires Personal Access Token with 'data.records:write' (or 'data.records:read' for 'get').
|
| airtable_manage_webhookA | Manages real-time Airtable Webhooks for bidirectional integrations with external platforms (Tally, Fillout, Stripe, PayPal, Make, Zapier, or custom backends). When to UseWhen you need instant notifications when records or schema change in an Airtable base. When configuring real-time sync pipelines to external data warehouses or webhook receivers. When listing, inspecting recent transaction payloads, or tearing down obsolete webhooks.
When NOT to UseDo NOT use this tool for batch data imports or record querying. Use 'airtable_batch_upsert' or 'airtable_query_records' instead. Do NOT use this tool to write automation logic inside Airtable. Use 'airtable_generate_automation_script' instead.
Operational DisclosuresSide Effects: 'create' registers a persistent HTTP webhook endpoint on Airtable's infrastructure. 'delete' permanently revokes delivery to that endpoint. Persistence: Webhooks persist on the base until explicitly deleted or until they expire after consecutive failed delivery attempts. Auth Scopes: Requires a Personal Access Token with the 'webhook:manage' scope. Rate Limits: Governed by Airtable's 5 req/sec API quota with automatic backoff retry.
|
| airtable_generate_automation_scriptA | Generates production-grade, syntactically verified JavaScript code tailored for Airtable's In-Base Scripting API ("Run a script" automation action). When to UseWhen configuring native Airtable Automations that require custom business logic, field transformations, or external API communication. When mapping incoming webhook payloads (Tally forms, Fillout, Stripe payment events) into structured Airtable records. When creating sequential prefixed IDs (e.g., 'VR-M-00105') without race conditions. When performing deduplication checks or cross-table rollups inside Airtable.
When NOT to UseDo NOT use this tool to execute operations directly on Airtable from your local machine. Use 'airtable_batch_upsert' or 'airtable_manage_records' instead. Do NOT use this tool for creating Interface Designer pages. Use 'airtable_create_interface_page' instead.
Operational DisclosuresExecution Environment: The generated code is designed to run in Airtable's native sandboxed Scripting environment with access to global 'base', 'input.config()', 'output.set()', and 'remoteFetchAsync()'. Safe & Idempotent: Generated templates include batching safeguards (Airtable's 50-record batch mutation limit) and error boundaries. No Side Effects Locally: This tool produces verified code text that you paste into the Airtable Automation Script editor.
|
| airtable_create_interface_pageA | Creates a new Interface Designer page (Dashboard, Kanban, Grid, or Record Review) inside an Airtable base using Chrome DevTools Protocol (CDP) browser automation. When to UseWhen building frontend web interfaces for your Airtable base so non-technical users or clients can interact with data without touching raw tables. When creating an Executive Dashboard with KPI summary cards, a Kanban board stacked by status, or a high-density Review Queue. When expanding an existing interface application with a new page.
When NOT to UseDo NOT use this tool to create backend database tables or columns. Use 'airtable_create_base_schema' or 'airtable_modify_schema' instead. Do NOT use this tool to configure Kanban stacking options on an existing page. Use 'airtable_configure_kanban' instead. Do NOT use this tool to publish interface draft changes to users. Use 'airtable_publish_interface' instead.
Operational DisclosuresPrerequisites: Requires Google Chrome running locally with remote debugging enabled (e.g. '--remote-debugging-port=9223') and an active Airtable login session. Side Effects: Automatically opens or switches to the base's Interface Designer in Chrome, toggles Edit Mode, and creates a draft page. Persistence: Changes remain in draft state until published using 'airtable_publish_interface'.
|
| airtable_rebrand_interfaceA | Renames the top-level interface brand title and sidebar navigation folder bundle via double-click CDP automation. When to UseWhen customizing an interface for a specific client brand, department, or internal application name (e.g. changing 'Untitled interface' to 'Vape Runners Merchant Portal'). When organizing sidebar pages into logical folders or bundles.
When NOT to UseOperational DisclosuresPrerequisites: Chrome running with '--remote-debugging-port=9223'. Side Effects: Selects and double-clicks the interface header title element and/or sidebar group label, committing new string values. Persistence: Saved to interface draft; must be published to become visible to end-users.
|
| airtable_configure_kanbanA | Configures an existing Kanban board page in Interface Designer by setting the stage-stacking singleSelect column and enabling front-of-card badges via Chrome CDP browser automation. When to UseWhen customizing an operational Kanban pipeline (e.g. Lead Pipeline, Candidate Tracker, Merchant Onboarding). When grouping vertical Kanban stacks by a specific single-select field (e.g. 'Status', 'Stage', 'Priority'). When unhiding front-of-card display pills (e.g. Client Name, Gross Volume, Plan Type) so card summaries are visible without opening the record.
When NOT to UseDo NOT use this tool to create a new Kanban interface page from scratch. Use 'airtable_create_interface_page' with layout_type='kanban' first. Do NOT use this tool to configure record detail side-sheets or locked columns. Use 'airtable_configure_detail_sheet' or 'airtable_set_field_permissions' instead.
Operational DisclosuresPrerequisites: Chrome must be open with '--remote-debugging-port=9223' on the target base. A Kanban interface page must already exist. Side Effects: Clicks into the right-hand properties sidebar, selects the stack-by dropdown, and toggles card badge visibility. Persistence: Saved to the interface draft; published live using 'airtable_publish_interface'.
|
| airtable_set_field_permissionsA | Sets column-level inline editing permissions on Grid and Record Review interfaces by toggling "Edit this column inline" ON or OFF via Chrome CDP browser automation. When to UseWhen locking permanent identifiers (e.g. ID, Receipt Number, Stripe Charge ID) so operational users cannot accidentally edit them. When protecting raw intake submissions or financial calculations from tampering. When keeping decision gates (e.g. Stage dropdown, Verification Checkbox, Review Notes) editable while keeping all other columns read-only.
When NOT to UseDo NOT use this tool for Kanban front-of-card badges. Use 'airtable_configure_kanban' instead. Do NOT use this tool to configure side-sheet popup field editability. Use 'airtable_configure_detail_sheet' instead.
Operational DisclosuresPrerequisites: Chrome running with '--remote-debugging-port=9223' with an open Interface Designer Grid or Review Queue page. Side Effects: Selects table column headers and toggles the inline editing switch in the right-hand properties sidebar. Persistence: Saved to interface draft; published live using 'airtable_publish_interface'.
|
| airtable_configure_detail_sheetA | Configures the expandable record detail side-sheet: enables record click-to-open and toggles field-level lock switches within the detail view via Chrome CDP browser automation. When to UseWhen setting up the opening detail card that pops out when an operational user clicks a row or Kanban card. When locking audit fields, billing totals, and created dates inside the side-sheet while allowing notes or stage toggles. When setting the primary header title field of the side-sheet.
When NOT to UseDo NOT use this tool for high-density table column inline edit permissions. Use 'airtable_set_field_permissions' instead. Do NOT use this tool to publish interface draft changes. Use 'airtable_publish_interface' instead.
Operational DisclosuresPrerequisites: Chrome running with '--remote-debugging-port=9223'. Side Effects: Clicks into the side-sheet configuration pane and adjusts record detail layout switches. Persistence: Saved to interface draft; published live using 'airtable_publish_interface'.
|
| airtable_publish_interfaceA | Finalizes and publishes all Interface Designer draft changes to production, confirming any multi-page confirmation modals via Chrome CDP browser automation. When to UseWhen you have finished building or modifying interface pages, Kanbans, and permissions, and want live users/clients to see the updates. As the final step in any automated interface creation workflow.
When NOT to UseOperational DisclosuresPrerequisites: Chrome running with '--remote-debugging-port=9223' on the target base. Side Effects: Clicks the blue 'Publish' button in the interface header and clicks confirmation dialogs. Persistence: Publishes all draft changes to all users with interface access.
|
