DATA OPS
BigQuery table-change webhook to Linear
Listens for a BigQuery table-update event via webhook, fetches the live schema, and opens a Linear ticket only when the column set or types actually changed (not on data-only…
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives BigQuery table-update eventHTTP webhook
- ActionFetch current BigQuery table schemaBigQuery
- LogicDiscard if only data changed; keep structural diffs
- ActionCreate Linear remediation ticketLinear
- ActionStore new schema as baselinePostgres
What it does
Reacts in near real time to BigQuery table updates. When a logging sink or audit event signals that a table was altered, it pulls the current schema and files a Linear ticket only if the structure — not just the rows — has shifted.
When to use it
Use it when you need fast notification rather than a once-a-day sweep, and your BigQuery dataset already emits change events through Cloud Logging or a pub/sub bridge. Ideal for tables feeding live ML features where a silent type change is expensive.
How it works
- 1An incoming webhook fires when BigQuery reports a table-update operation.
- 2The flow calls BigQuery to read the table's current `schema.fields` definition.
- 3A logic step compares the field list and modes against the last stored shape and discards the event if only data changed.
- 4When structure differs, it assembles a human-readable diff of added, removed, and retyped fields.
- 5A Linear issue is opened on the owning team with the dataset, table, and diff, then the new schema is saved as the baseline.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.