Airtable Record Digest

Pulls records from an Airtable table and sends a digest of the record data to the workflow's subscribers. Useful as a scheduled "what's in this table right now" snapshot — e.g. an ops table, a CRM pipeline, a content calendar.

Use case

You keep your work (tasks, leads, content pipeline, inventory, etc.) in an Airtable base. Instead of opening Airtable to check it, this workflow calls the Airtable API on a schedule and delivers the current records to your InTouch subscribers on whatever channel they're configured for (email, Slack, etc.).

What it does each run

1. fetchRecords (airtable connector, operation: list-records) — calls the Airtable API for the configured base + table and publishes: - {{fetchRecords.result}} — the raw list-records API response as a JSON string - {{fetchRecords.status}} — the HTTP status code
2. notify (message tool) — sends a digest to the workflow's contacts (user intouch) containing the HTTP status and the raw JSON record payload from step 1.

If the fetch fails, the intouch user is alerted (alertOnError: true).

The message carries the connector's raw result. If you want a human-readable summary instead of raw JSON, insert a runtimeenv (script) or ai task between the two steps that consumes {{fetchRecords.result}} and publishes its own output for the message body.

Required credentials

• Airtable API key / Personal Access Token — supplied to the airtable connector's apiKey property. Create a PAT at https://airtable.com/create/tokens with the data.records:read scope and access to the base you want to digest. In workflow.yaml this is the placeholder <set via credential>; bind it to an InTouch credential (or a runtime env var) at install time. Never hardcode the key in the YAML.

Required configuration (runtime environment variables)

• AIRTABLE_BASE_ID — the Airtable base ID (e.g. appXXXXXXXXXXXXXX)
• AIRTABLE_TABLE_NAME — the table name (or table ID) to digest

Tools used

• airtable (connector — apiKey + operation + params -> result, status)
• message (built-in — notifies the workflow's contacts)

Scheduling

Attach a schedule (e.g. every morning, or hourly during business hours) so the digest arrives on a cadence that suits your team.