OTHER
Datadog team budget breach escalation
Tracks month-to-date Datadog spend per team against assigned budgets and escalates via PagerDuty plus Slack when a team is projected to overshoot its monthly cap.
How it runs
The automated pipeline, trigger to output.
- TriggerMultiple-times-daily schedule
- ActionFetch month-to-date cost by teamDatadog
- LogicProject month-end and classify vs budget
- ActionOpen PagerDuty incident for hard breachesPagerDuty
- OutputPost tiered budget digest to SlackSlack
What it does
This workflow enforces per-team observability budgets. Several times a day it compares each team's month-to-date Datadog spend against its assigned budget, projects end-of-month spend from the current run rate, and escalates the teams on track to blow their cap — paging on-call for hard breaches and posting a softer heads-up for early warnings.
When to use it
Use it when teams have committed observability budgets and overruns need an owner and a response, not just a dashboard nobody checks. Best where finance has set real caps and wants enforcement with escalation tiers.
How it works
- 1A schedule runs the check a few times per day.
- 2The Datadog action fetches month-to-date cost grouped by team tag.
- 3A logic step projects month-end spend from the run rate and classifies each team as ok, warning, or breach against its budget.
- 4For hard breaches a PagerDuty action opens an incident routed to the team's service.
- 5The output step posts a tiered budget-status digest to Slack, highlighting warnings and confirming the paged breaches.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
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.