PERSONAL PRODUCTIVITY

Escalate repeatedly-stale meeting agendas to the meeting's manager

Tracks how many cycles a recurring Google Calendar meeting has run without a refreshed agenda and, once it crosses a threshold, escalates to the organizer's manager in Microsoft…

CategoryPersonal Productivity
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionRead recurring events + agenda timestampsGoogle CalendarGoogle Calendar
  • ActionUpdate per-series stale streak counterPostgreSQLPostgres
  • LogicBranch on streak >= escalation threshold
  • OutputPost escalation card to manager in TeamsMicrosoft Teams

What it does

Catches meetings that have quietly gone on autopilot for weeks. It keeps a running count of consecutive occurrences where a recurring Google Calendar meeting's agenda went unchanged, and when that streak crosses a set threshold it stops nudging the owner and instead escalates to their manager — prompting a real decision: refresh the format, reassign the owner, or kill the meeting.

When to use it

When gentle reminders aren't working and you want a governance backstop so zombie meetings get reviewed rather than running forever. Useful for chiefs of staff and ops leads auditing recurring-meeting load.

How it works

  1. 1A weekly schedule fires the audit.
  2. 2It reads recurring events from Google Calendar and their last-modified agenda timestamps.
  3. 3A logic step increments a per-series stale-streak counter stored in Postgres, resetting any series whose agenda changed.
  4. 4A branch checks whether the streak meets the escalation threshold (e.g. three cycles).
  5. 5For meetings over threshold it posts an escalation card to the manager in Microsoft Teams with the streak count and decision options.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.