DATA OPS
CSV Feed Validation with Airtable Defect Tracker
On a schedule, pulls the latest partner CSV from Google Drive, validates it against a schema, loads clean rows to Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled daily run
- ActionDownload latest partner CSV from Google DriveGoogle Drive
- LogicValidate each row against contract schema
- LogicBranch passing rows from failing rows
- ActionUpsert clean rows into Airtable data tableAirtable
- ActionCreate one defect record per bad row in AirtableAirtable
- OutputPost run digest to SlackSlack
What it does
This workflow runs on a schedule, grabs the newest partner CSV from a Google Drive folder, and validates every row against your contract schema. Clean rows are written into an Airtable base; bad rows become individual defect records in a tracker table, tagged with the failure reason and the partner who sent them.
When to use it
Use it when an ops team owns data quality in Airtable and needs a human-friendly worklist of defects rather than a raw file dump. Each defect becomes a trackable record someone can assign, comment on, and close.
How it works
- 1A scheduled trigger fires (for example, every morning).
- 2The latest CSV in the watched Google Drive folder is downloaded.
- 3Each row is validated against the schema — required columns, formats, and allowed values.
- 4The flow branches passing rows from failing rows.
- 5Passing rows are upserted into the Airtable data table.
- 6Each failing row is created as a defect record in Airtable with the rule it broke and the source partner.
- 7A digest of the run is posted to Slack for the on-call data steward.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.