SUMMARIZATION
Weekly Standup Rollup to Notion Blocker Tracker
On a weekly schedule, collects five days of Discord standup threads, builds a per-person trend of recurring blockers.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly end-of-week schedule
- ActionPull the week of standup threads from DiscordDiscord
- ActionCluster by person and detect recurring blockers with OpenAIOpenAI
- LogicSplit resolved vs still-open blockers
- ActionCreate the rollup narrative page in NotionNotion
- OutputAppend open blockers to Notion tracker tableNotion
What it does
It rolls a full week of async standups into one digestible report. Instead of a single day's snapshot, it reads every standup thread across the week, identifies blockers that keep reappearing for the same person, and produces a per-person trend view. The output lands in Notion as a narrative rollup page and a structured tracker table of open blockers and their owners.
When to use it
Use it for a weekly team review or a manager's Friday wrap-up, when you want to spot chronic blockers and ownership gaps rather than firefight a single day. Good for leads who run retros off Notion.
How it works
- 1A weekly schedule trigger fires at end of week.
- 2The flow pulls the week's standup threads from the Discord channel.
- 3OpenAI clusters updates by person and detects blockers that recurred across multiple days, attributing each to an owner.
- 4A logic step separates newly resolved blockers from still-open ones.
- 5A Notion page is created with the per-person narrative rollup.
- 6Each open blocker is appended as a row in a Notion blocker tracker database with owner and age.
Set it up
What you configure once, before turning it on.
- 1Connect DiscordCommunity channels + voice + bots.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.