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.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: series breached both thresholdsHTTP webhook
- ActionLook up series owner and recent statsGoogle Calendar
- ActionDM owner with evidence and Cancel/Keep/Shrink buttonsSlack
- LogicInterpret owner response
- OutputApply choice to the calendar eventGoogle 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
- 1The flow triggers on a webhook from your detector when a series breaches both thresholds.
- 2It looks up the series owner and recent stats in Google Calendar.
- 3It DMs the owner on Slack with evidence and Cancel/Keep/Shrink buttons.
- 4A branch interprets the owner's response.
- 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.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect Google CalendarEvents, attendees, availability.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
