PERSONAL PRODUCTIVITY

Cancel-or-Merge Proposal Drafter for Stale Syncs

Detects recurring meetings with chronic low attendance over the trailing month and uses an agent to draft a personalized cancel or merge proposal.

CategoryPersonal Productivity
Enginepaperclip
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionPull 4-week attendance historyGoogle CalendarGoogle Calendar
  • LogicIsolate chronically under-attended meetings
  • ActionDraft tailored cancel/merge proposalOpenAI
  • OutputDM proposal to owner for approvalSlack

What it does

It does the awkward part for you: spotting a dying standing meeting and writing the tactful note that proposes killing or merging it. Instead of a raw list, the meeting owner gets a ready-to-send draft tailored to their specific meeting.

When to use it

Use it when flagging meetings isn't enough and the bottleneck is the social cost of proposing a cancel. Best for orgs where meeting owners, not a central admin, make the final call.

How it works

  1. 1A weekly schedule fires.
  2. 2The flow gathers the trailing 4 weeks of recurring meetings and acceptance data from Google Calendar.
  3. 3A logic step isolates meetings averaging under 40% attendance with no clear decision output.
  4. 4For each one, an agent drafts a personalized proposal: cancel outright, merge into a related sync, or drop to biweekly — with reasoning grounded in that meeting's own numbers.
  5. 5The draft is DM'd to the meeting owner in Slack with approve/edit buttons, so nothing changes without a human yes.

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 OpenAIModels, embeddings, 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.