airtable

To safely write Airtable records, you must validate field ids and types against table schema metadata offline before submission. This schema-aware approach refuses writes to computed or read-only fields, preventing bad payloads and unintended destructive actions.

You can filter Airtable records using filterByFormula and paginate through the results. The skill supports paginated record retrieval, single-record fetches by id, and optional views to refine your query scope.

You can discover accessible Airtable bases and inspect table schemas to prepare accurate requests. The skill lists base tables, fields, and select choices, enabling field-aware validation and schema-based payload preparation before executing read or write operations.

Yes, Airtable API operations require a personal access token (PAT) for bearer authentication. The PAT must be stored in HybridClaw secrets to authorize base discovery, record querying, schema validation, and guarded write operations.

Updating Airtable attachment fields involves building payloads from public http(s) URLs. The skill applies safety checks against private or internal network targets to ensure only accessible attachment sources are used in record updates.

Deleting an Airtable record without explicit operator approval is refused by the skill. Guarded deletions require explicit operator grant to proceed, preventing unintended destructive actions and ensuring safe record management during workflow execution.