OTHER
Datadog daily spend attribution by team
Pulls yesterday's Datadog usage and cost data, maps each line item to an owning team via tag rules, and posts a ranked spend breakdown to Slack every morning.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule after usage finalizes
- ActionFetch Datadog usage and cost by tagDatadog
- LogicMap usage rows to owning team via tags
- ActionRoll up per-team totals and day-over-day deltas
- OutputPost ranked spend breakdown to SlackSlack
What it does
Every morning this workflow turns raw Datadog usage into a per-team cost ledger. It reads the prior day's metered usage (logs, hosts, custom metrics, APM), attributes each charge to a team using your `team:` / `service:` tag mapping, and posts a ranked breakdown to Slack so engineering leads see what they spent before standup.
When to use it
Run it when observability is one shared bill nobody owns and you need daily, team-level accountability instead of a surprise at month end. Ideal for platform teams doing FinOps showback across many squads.
How it works
- 1A daily schedule fires shortly after Datadog finalizes the previous day's usage.
- 2The Datadog action fetches hourly usage and estimated cost by product and by tag.
- 3A logic step joins each usage row to an owning team using your tag-to-team mapping, bucketing untagged spend into an "unattributed" pool.
- 4An action rolls the rows into per-team totals, day-over-day deltas, and a top-spenders ranking.
- 5The output step posts the formatted leaderboard to a Slack FinOps channel, calling out the largest movers.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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 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.