PERSONAL PRODUCTIVITY

Stale-Meeting Owner Nudge with Coda Tracker

Detects recurring meetings missing an agenda before they happen and DMs each meeting owner a private nudge.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule (afternoon)
  • ActionFetch tomorrow's recurring meetings from Google CalendarGoogle CalendarGoogle Calendar
  • LogicBranch on whether agenda exists and has content
  • ActionDM organizer a private nudge in SlackSlack
  • OutputLog flagged meeting to Coda decay trackerCodaCoda

What it does

It catches recurring meetings that are about to happen with no agenda and quietly nudges the organizer directly, then records the lapse in a Coda table so you can see who chronically skips prep.

When to use it

Use it when you want gentle accountability rather than a public callout — nudging owners 24 hours ahead and building a paper trail of which meetings keep showing up unprepared.

How it works

  1. 1A daily schedule runs each afternoon.
  2. 2It fetches recurring meetings on tomorrow's Google Calendar.
  3. 3For each one it checks whether an agenda doc exists and has content for the upcoming instance.
  4. 4A branch separates meetings with a ready agenda from those that are empty or missing.
  5. 5For each empty meeting it sends the organizer a private Slack DM asking them to add an agenda or cancel.
  6. 6It appends a row to a Coda decay tracker with the meeting name, owner, and date so repeat offenders surface over time.

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.