SUMMARIZATION
Standup Blocker Owner Callout via Teams DM
After a standup is posted in Microsoft Teams, identifies each blocker's owner and direct-messages that owner a personalized callout listing exactly who is waiting on them and why.
How it runs
The automated pipeline, trigger to output.
- TriggerNew standup message in Microsoft TeamsMicrosoft Teams
- ActionBuild per-blocker owner map with OpenAIOpenAI
- LogicGroup blockers by owner
- ActionDM each owner a personalized callout in TeamsMicrosoft Teams
- OutputPost blocker map summary to the channelMicrosoft Teams
What it does
It closes the loop between a blocker being mentioned and the person who can actually clear it. After the standup posts, it reads the thread, figures out who owns each blocker, and sends each owner a private Teams message naming the blocked teammates and the specific items waiting on them. No public shaming, just direct nudges.
When to use it
Use it when blockers get raised in standup but the owners never notice because they skim the channel. Ideal for teams on Microsoft Teams that want gentle, targeted accountability instead of a wall of @-mentions.
How it works
- 1A new standup message in the Teams channel triggers the flow.
- 2OpenAI reads the thread and produces a per-blocker map of who is blocked and which owner must act.
- 3A logic step groups blockers by owner so each person gets one consolidated message.
- 4For each owner with open blockers, a personalized direct message is sent in Teams listing the waiting teammates and items.
- 5A short blocker map summary is posted to the channel for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, files.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.