DEVOPS
Publish a weekly per-team cloud chargeback digest with spike callouts to Notion
Every Monday it aggregates the prior week's cloud spend by owning team from BigQuery, flags any team whose spend rose materially week over week.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionRoll up spend by team, week over weekBigQuery
- LogicRank teams and flag spike threshold crossings
- OutputPublish chargeback digest page to NotionNotion
What it does
Builds a weekly chargeback report that splits total cloud spend across owning teams, compares each team to the previous week, and highlights the teams responsible for the largest increases. It publishes the result as a clean Notion page so leadership and team leads have a shared, durable record of who spent what.
When to use it
Use it when you run a showback or chargeback model and want a repeatable weekly artifact instead of ad hoc spreadsheets. Good for finance-engineering syncs and budget reviews where attribution to teams matters.
How it works
- 1A weekly Monday schedule kicks off the run.
- 2A BigQuery query rolls up last week's spend grouped by owning team and compares it to the prior week.
- 3A logic step ranks teams by week-over-week dollar increase and tags any that crossed the spike threshold.
- 4An output step renders a Notion page: a summary table of all teams plus a "spikes this week" section at the top with the biggest movers and their likely drivers.
- 5The page is created under the FinOps Notion database, dated for the week.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect NotionPages, databases, comments.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.