DATA OPS
Postgres Replica Drift Watcher to Asana Backlog
Compares your application Postgres read-replica schema against the dbt source contract and files an Asana task whenever app developers add or change columns the analytics layer…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule triggers source check
- ActionQuery Postgres replica information_schemaPostgres
- LogicDiff live source schema vs. dbt source contract
- LogicExit if no undocumented changes
- OutputCreate Asana task in analytics backlog with deltasAsana
What it does
Most drift comes from the application database, not the warehouse. This workflow watches your Postgres read-replica's `information_schema`, compares the source tables to the dbt source contract that analytics relies on, and files an Asana task when app developers ship a column the contract does not know about. It closes the gap between product shipping a migration and analytics noticing.
When to use it
Use it when your dbt sources sit directly on an app Postgres database and product engineers change that schema on their own cadence. It gives the analytics team a standing backlog item the moment a source column is added, renamed, or retyped, instead of discovering it through a broken model weeks later.
How it works
- 1A daily schedule triggers the source check.
- 2Query the Postgres replica `information_schema` for source-table columns.
- 3Load the dbt source contract describing expected source shapes.
- 4Diff live source schema vs. contract and collect undocumented changes.
- 5If nothing changed, exit; otherwise create an Asana task in the analytics backlog.
- 6The task lists each new or changed column with the table and detected timestamp.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.