PERSONAL PRODUCTIVITY

Flag low-value recurring meetings and nudge owners on Slack

Reads the meeting-cost table in Coda, flags recurring meetings whose computed cost exceeds a threshold while attendance keeps dropping.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires after cost refresh
  • ActionRead meeting-cost rows from CodaCodaCoda
  • LogicFlag high-cost, low-attendance meetings
  • LogicBuild tailored recommendation per meeting
  • ActionDM each meeting owner on SlackSlack
  • OutputWrite flagged status and nudge date back to CodaCodaCoda

What it does

This workflow closes the loop between measuring meeting cost and actually acting on it. It reads your existing Coda cost table, applies a low-value test (high dollar cost combined with declining or low attendance), and reaches out to each flagged meeting's owner on Slack with a specific, polite recommendation.

When to use it

Use it once you already track meeting cost in Coda and want gentle, automated accountability instead of a quarterly meeting purge. Ideal for teams trying to build a self-correcting meeting culture.

How it works

  1. 1A weekly schedule starts the run after the cost-audit workflow has refreshed the Coda table.
  2. 2The flow reads all rows from the Coda meeting-cost table.
  3. 3It filters to meetings where dollar cost is above the threshold and attendance ratio is below target, marking them low value.
  4. 4For each flagged meeting it builds a tailored recommendation: cancel, halve the duration, or cut optional attendees.
  5. 5It looks up the owner's Slack handle from the row and sends a direct message with the cost figure and the suggestion.
  6. 6It writes a flagged flag and the date of the nudge back to the Coda row so owners are not pinged twice in the same cycle.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.