SUMMARIZATION
Monthly voice-of-customer trend rollup with month-over-month shifts
Once a month, reads the archive of weekly VoC briefs in Notion, computes which themes are rising or fading.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly first-business-day schedule
- ActionRead trailing-month VoC briefs from NotionNotion
- LogicAggregate counts, compute month-over-month deltas
- ActionDraft rising/fading/new theme narrativeOpenAI
- OutputPost trend digest to leadership SlackSlack
What it does
Elevates weekly customer themes into a monthly trend story leadership can act on. It reads the month's archive of voice-of-customer briefs already stored in Notion, aggregates theme frequencies across all weeks, and compares them to the prior month to surface what is accelerating, what is cooling, and what is brand new. OpenAI then writes a short narrative explaining the shifts, which lands in a leadership Slack channel.
When to use it
Use this when weekly briefs are piling up but no one is connecting the dots across time, and leadership keeps asking "is this getting better or worse?" It turns a stack of snapshots into a directional read on customer sentiment and demand.
How it works
- 1A monthly schedule triggers the rollup on the first business day.
- 2It reads all weekly VoC brief pages from the Notion archive database for the trailing month.
- 3A logic step aggregates theme counts and computes month-over-month deltas versus the prior period.
- 4OpenAI drafts a narrative of rising, fading, and emerging themes with representative evidence.
- 5The summary posts to a leadership Slack channel as a threaded digest.
Set it up
What you configure once, before turning it on.
- 1Connect NotionPages, databases, comments.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.