DATA OPS
On-demand schema-change webhook triage with GitHub PR diff
Receives a schema-change webhook from your ELT tool, fetches the affected table's current schema.
How it runs
The automated pipeline, trigger to output.
- TriggerELT schema-change webhook receivedHTTP webhook
- ActionQuery affected table's current schemaSnowflake
- ActionRead committed schema-as-code fileGitHub
- LogicRender updated file content from diff
- OutputOpen GitHub PR with schema updateGitHub
What it does
This workflow turns an ELT schema-change notification into a reviewable code change. When a webhook fires for a changed table, it pulls the live schema from the warehouse, reads the committed schema-as-code file from GitHub, and opens a pull request with the file updated to match reality. Reviewers see exactly what changed as a Git diff and approve or block it like any other code change.
When to use it
Use it when your team treats warehouse schemas as version-controlled artifacts and wants every upstream change to flow through code review instead of landing silently. Ideal for teams enforcing data contracts via PR approval.
How it works
- 1The ELT tool sends a schema-change webhook to the trigger.
- 2It queries the warehouse for the affected table's current columns and types.
- 3It reads the existing schema-as-code file from the GitHub repo.
- 4A logic step renders the updated file content reflecting the new schema.
- 5It opens a GitHub pull request with the change on a new branch.
- 6The PR body lists added, removed, and retyped fields for the reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.