SUMMARIZATION
Daily harvest with dedupe against the existing macro library
Harvests solved Discord threads daily, then compares each new answer candidate against the existing Notion macro library so only genuinely new knowledge is queued.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts the harvest
- ActionPull resolved threads and read existing macrosDiscord
- ActionSummarize and embed each candidate questionOpenAI
- LogicRoute as new, near-duplicate, or already-covered
- OutputQueue new rows or comment edits on existing Notion macrosNotion
What it does
It runs the daily Discord harvest but adds a deduplication brain: before queuing a candidate, it checks whether your macro library already covers that question. Truly new topics become review candidates; near-matches get attached to the existing macro as a suggested improvement, so the library sharpens instead of bloating.
When to use it
When your macro library is already sizable and a raw harvest would flood reviewers with rephrased versions of answers you already have. This keeps the review queue high-signal.
How it works
- 1A daily schedule starts the harvest.
- 2The flow pulls the last day of resolved Discord threads and reads existing macros from Notion.
- 3OpenAI summarizes each thread and embeds the question for semantic comparison against current macros.
- 4A logic step routes each candidate: new, near-duplicate, or covered-and-ignored.
- 5New candidates create review rows in Notion; near-duplicates post a suggested edit comment on the matching macro page.
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.