DATA OPS
Apply confirmed team mappings back to BigQuery on Notion approval
When a FinOps reviewer confirms the owning team on a Notion review card, a webhook fires and the workflow rewrites the attribution rows for that principal in BigQuery and adds…
How it runs
The automated pipeline, trigger to output.
- TriggerNotion status-change webhook (card set to Confirmed)HTTP webhook
- LogicValidate payload; proceed only on Confirmed transition
- ActionRewrite attribution rows for the principal in BigQueryBigQuery
- ActionUpsert principal to owner lookup tableBigQuery
- OutputComment confirmation back on the Notion cardNotion
What it does
Closes the attribution loop: a confirmed team on a Notion card triggers a rewrite of that principal's attribution rows in BigQuery and records the mapping permanently so the heuristic never has to guess for that principal again.
When to use it
Use it as the action half of a human-in-the-loop attribution flow. Once someone says 'this service account belongs to Growth,' the decision should stick and propagate, not get re-asked next week.
How it works
- 1Notion sends a webhook when a review card's status flips to Confirmed.
- 2Validate the payload and extract the principal and chosen team.
- 3Branch: ignore events that are not a Confirmed transition.
- 4Update every attribution row for that principal to the confirmed team at full confidence in BigQuery.
- 5Upsert the principal-to-team mapping into the owner lookup table so future runs match deterministically.
- 6Reply on the originating Notion card with how many rows were corrected and the dollars now attributed.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BigQueryDatasets, queries, schemas.
- 3Connect NotionPages, databases, comments.
- 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.