DATA OPS

Nudge Owners of Unlabeled BigQuery Jobs via Slack DM

Finds expensive BigQuery jobs that ran without a team label, looks up the user who ran them, and sends each person a private Slack DM asking them to start labeling.

CategoryData Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily morning schedule
  • ActionFind unlabeled high-cost jobs with owner emailGoogle BigQueryBigQuery
  • LogicAggregate by user and resolve Slack member
  • ActionDM each owner their unlabeled jobsSlack
  • OutputIncrement repeat-offender tally in CodaCodaCoda

What it does

Closes the attribution gap by hunting for high-cost jobs missing a `team` label, mapping the BigQuery `user_email` to a Slack user, and privately nudging each owner to label their work so cost reports stay clean.

When to use it

When your cost-by-team reports are undermined by a big "unattributed" bucket. Use it to drive labeling hygiene through gentle, direct, repeated reminders instead of blanket channel scolding.

How it works

  1. 1A scheduled trigger runs each morning.
  2. 2A BigQuery action selects yesterday's jobs above a bytes-billed threshold where the `team` label is null, returning `user_email` and cost.
  3. 3A logic step aggregates cost per user and resolves each email to a Slack member.
  4. 4A Slack action sends each owner a DM listing their unlabeled jobs and the dollar impact, with labeling instructions.
  5. 5A Coda action increments a repeat-offender tally so persistent gaps surface for a manager follow-up.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect CodaDocs, packs, automations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.