PERSONAL PRODUCTIVITY

Meeting Owner Cancel-Approval Loop via Slack

When a recurring series crosses both low-attendance and no-decision thresholds, DMs the meeting owner on Slack with the evidence and Cancel/Keep/Shrink buttons.

CategoryPersonal Productivity
EngineSim + Paperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook: series breached both thresholdsHTTP webhook
  • ActionLook up series owner and recent statsGoogle CalendarGoogle Calendar
  • ActionDM owner with evidence and Cancel/Keep/Shrink buttonsSlack
  • LogicInterpret owner response
  • OutputApply choice to the calendar eventGoogle CalendarGoogle Calendar

What it does

This workflow closes the loop between detecting a dead meeting and actually killing it. When a recurring series trips both guardrails — attendance below target and no recorded decisions over the lookback window — the flow sends the meeting's owner a direct Slack message summarizing the evidence and offering three choices: cancel the series, keep it, or shrink the invite list. Based on the owner's reply, it updates the Google Calendar event automatically, so the audit produces a real change rather than another ignored report.

When to use it

Use this when reports alone never lead to action. By routing the decision to the one person who owns the meeting and making the action a single click, it removes the friction that keeps zombie meetings alive. Best paired with an upstream detector that supplies the attendance and decision data.

How it works

  1. 1The flow triggers on a webhook from your detector when a series breaches both thresholds.
  2. 2It looks up the series owner and recent stats in Google Calendar.
  3. 3It DMs the owner on Slack with evidence and Cancel/Keep/Shrink buttons.
  4. 4A branch interprets the owner's response.
  5. 5It applies the choice by canceling, leaving, or trimming attendees on the calendar event.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect Google CalendarEvents, attendees, availability.
  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.