Airtable Automation
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Airtable automation skill, but it can use a connected Airtable account to change or delete business data, so users should review permissions and confirm destructive actions.
Before installing, make sure you trust Rube/Composio and connect only the Airtable access you actually need. Treat bulk updates, deletes, and schema changes as high-impact actions and confirm them explicitly before letting the agent proceed.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent could change or delete Airtable records when acting on a user request.
The skill documents Airtable tools that can create, modify, or delete records. This is purpose-aligned for Airtable automation, but these are high-impact actions if used on important bases.
`AIRTABLE_CREATE_RECORD` / `AIRTABLE_UPDATE_RECORD` / `AIRTABLE_DELETE_RECORD` / `AIRTABLE_DELETE_MULTIPLE_RECORDS`
Use the skill only with bases you intend to automate, and require manual confirmation for deletes, bulk updates, imports, and schema changes.
If connected with a broad Airtable account, the agent may be able to access or modify more bases and tables than intended.
The skill depends on a delegated Airtable connection through Rube/Composio. This is expected for the integration, but it gives the agent authority according to the connected Airtable account's permissions.
Active Airtable connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `airtable`
Connect with the least-privileged Airtable account or workspace access available, review the granted scopes, and revoke the connection when it is no longer needed.
Airtable metadata, records, and requested changes may be routed through Rube/Composio as part of normal operation.
A third-party MCP endpoint mediates the Airtable operations. This is disclosed and central to the skill, but users should recognize that Airtable requests and results pass through that integration path.
Add `https://rube.app/mcp` as an MCP server
Use this only if you trust the Rube/Composio MCP service and its handling of Airtable data.