PERSONAL PRODUCTIVITY

New Recurring Meeting Justification Guardrail

When a new recurring meeting is created on a team calendar, intercepts it and asks the organizer to log a purpose, end date, and owner in Coda before it becomes a permanent…

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew recurring meeting createdGoogle CalendarGoogle Calendar
  • LogicFilter to true recurring series only
  • ActionDM organizer a justification formSlack
  • LogicBranch on response vs 3-day timeout
  • OutputAppend justification to Coda registryCodaCoda

What it does

It stops zombie meetings at birth. The moment someone schedules a new recurring event, this flow asks the organizer to justify it — purpose, success signal, and a review date — and records that in a Coda registry so every standing meeting has an accountable owner.

When to use it

Use it when the real problem is meetings being created carelessly, not just old ones lingering. A lightweight gate that builds intentional meeting culture without blocking anyone.

How it works

  1. 1An event trigger fires when a new recurring meeting is created on the watched Google Calendar.
  2. 2A filter ignores one-off events and short ad-hoc syncs, keeping only true recurring series.
  3. 3The flow DMs the organizer in Slack with a short form: purpose, expected outcome, owner, and a mandatory review-by date.
  4. 4On submit, the answers plus meeting metadata are appended to a Coda meeting registry.
  5. 5If the organizer doesn't respond within 3 days, the meeting is escalated in the registry as unjustified for later review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  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.