DATA OPS
Airtable field-change daily digest to Slack
Tracks field additions, removals, and type changes across a set of Airtable bases used as a data source and posts a single consolidated drift digest to Slack each morning.
How it runs
The automated pipeline, trigger to output.
- TriggerMorning schedule fires
- ActionRead field metadata from Airtable schema APIAirtable
- LogicDiff each base vs. baseline; collect all changes
- OutputPost consolidated drift digest to SlackSlack
- ActionSave new schemas as baselinesPostgres
What it does
Monitors the field schema of business-critical Airtable bases — the ones operations teams quietly restructure — and rolls every structural change into one daily Slack digest instead of noisy per-change pings, so data consumers know what shifted before they sync.
When to use it
Use it when Airtable is an upstream of record that non-technical teams edit freely. A weekly surprise like a renamed field or a single-select turned into multi-select silently breaks your ingestion; a morning digest gives you a heads-up window.
How it works
- 1A morning schedule starts the run.
- 2The flow reads each watched base's table-and-field metadata from the Airtable schema API.
- 3A logic step diffs every base against its stored baseline, collecting added fields, removed fields, and changed field types.
- 4If no base changed, the run ends silently; otherwise it formats one grouped digest organized by base and table.
- 5The digest posts to a Slack channel, and each base's new schema is saved as the next baseline.
Set it up
What you configure once, before turning it on.
- 1Connect AirtableBases, tables, views, automations.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.