PERSONAL PRODUCTIVITY
Overlapping Meeting Merge-Candidate Finder
Weekly, compares recurring meetings across the team to find series with heavily overlapping attendee lists and similar topics.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch all recurring series with attendeesGoogle Calendar
- LogicBuild attendee sets and topic signatures
- LogicCompute pairwise overlap, keep candidates above threshold
- OutputPost proposed merge pairings to SlackSlack
What it does
This workflow hunts for redundant recurring meetings that could be combined. Each week it collects all recurring series, builds an attendee set and a topic signature for each (from titles and descriptions), and compares every pair. When two series share most of their attendees and cover similar ground, the flow proposes them as a merge candidate. The owner gets a Slack message listing each suggested pairing with the overlap percentage and a recommended single replacement slot.
When to use it
Use this when the same group of people sits in three different standing meetings that all blur together. Instead of manually diffing calendars, you get an automated shortlist of "these two could be one meeting," which is the fastest way to reclaim hours without cutting any real coverage.
How it works
- 1A weekly schedule triggers the audit.
- 2The flow fetches all recurring series from Google Calendar with their attendees and descriptions.
- 3It builds attendee sets and topic signatures, then computes pairwise overlap.
- 4A filter keeps only pairs above the attendee-overlap and topic-similarity thresholds.
- 5Proposed merge pairings are posted to Slack with overlap scores and a suggested consolidated time.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.