AI AGENTS
Post-Meeting Follow-Up and Action Tracker
When a calendar meeting ends, drafts a recap-and-next-steps follow-up email to attendees and logs the extracted action items as tasks in Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerCalendar meeting endsGoogle Calendar
- ActionFetch event details and notesGoogle Calendar
- ActionDraft recap and extract action itemsOpenAI
- ActionSave follow-up email as draftGmail
- OutputLog action items in NotionNotion
What it does
After a meeting wraps, the workflow reads the event details and any notes on it, has OpenAI produce a clean recap with explicit next steps and owners, drafts that follow-up email to the attendees, and writes each action item into a Notion tracking database so nothing falls through the cracks.
When to use it
When meetings end and the follow-up never gets sent and the to-dos never get logged. This turns the close of every meeting into a drafted recap plus a tracked action list automatically.
How it works
- 1A Google Calendar event ending triggers the run.
- 2Google Calendar returns the event's attendees, description, and attached notes.
- 3OpenAI writes a recap email and extracts structured action items with owners and due dates.
- 4Gmail saves the recap as a draft addressed to attendees for your review.
- 5Notion creates one task row per action item in your tracker database.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.