PERSONAL PRODUCTIVITY

Cost-check every newly created recurring meeting

When a new recurring meeting appears on the team calendar, instantly estimates its annualized cost from attendee count and cadence, logs it to a Coda watchlist.

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Google Calendar event createdGoogle CalendarGoogle Calendar
  • LogicSkip if not a recurring series
  • LogicCompute annualized cost from recurrence rule
  • ActionAppend meeting to Coda watchlistCodaCoda
  • LogicBranch on annual cost vs guardrail
  • OutputWarn organizer on Slack if over thresholdSlack

What it does

This workflow catches expensive recurring meetings at the moment they are created, before they become permanent fixtures. It estimates the full annualized cost of the new series (attendees x duration x occurrences-per-year x hourly rate), records it in a Coda watchlist, and gives the organizer a heads-up if the number is large.

When to use it

Use it to put a soft guardrail on calendar sprawl. It suits organizations where anyone can spin up a weekly sync and nobody sees the cumulative annual price tag until it is entrenched.

How it works

  1. 1A calendar event trigger fires when a new event is created.
  2. 2The flow checks whether the event is recurring; non-recurring events are ignored.
  3. 3It derives occurrences per year from the recurrence rule and computes annualized cost from attendees, duration, and the hourly rate.
  4. 4It appends a row to the Coda watchlist with the meeting, organizer, and projected yearly cost.
  5. 5A branch checks the annual cost against the guardrail threshold.
  6. 6If over threshold, it sends the organizer a Slack message showing the yearly cost and asking them to confirm the series is worth it.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.