OTHER
Datadog untagged spend cleanup tickets
Finds Datadog cost that lacks a team or service tag, identifies the likely owner from related resources, and files Linear tickets so the spend gets properly attributed.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull untagged Datadog cost and resourcesDatadog
- LogicInfer likely owner and rank by cost
- LogicFilter out low-cost sources
- ActionFile Linear cleanup ticketsLinear
- OutputPost weekly cleanup summary to SlackSlack
What it does
This workflow drives down your "unattributed" cost bucket. Weekly it surfaces Datadog spend with no `team` or `service` tag, infers the probable owner from co-located resources and host metadata, and files a Linear cleanup ticket per orphaned cost source so someone tags it. Over time the unattributed pool shrinks and showback gets accurate.
When to use it
Use it when a meaningful slice of your Datadog bill can't be charged back because resources are untagged, and you want a steady, tracked cleanup loop instead of a one-off tagging sprint.
How it works
- 1A weekly schedule triggers the audit.
- 2The Datadog action pulls cost and resources where the ownership tags are missing.
- 3A logic step groups orphaned spend by resource and infers a likely owning team from neighboring tagged resources, ranking by dollar impact.
- 4A logic filter drops sources below a cost threshold to avoid ticket noise.
- 5A Linear action files a cleanup ticket per significant source with the suggested owner and the cost at stake.
- 6The output step posts a weekly summary of opened tickets and total unattributed spend to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.