SUMMARIZATION
Extract decisions from resolved Front threads into a Notion registry
When a Front conversation is archived, an AI reads the full thread, pulls out every decision that was made.
How it runs
The automated pipeline, trigger to output.
- TriggerFront conversation archived/resolvedFront
- ActionFetch full conversation message historyFront
- ActionExtract discrete decisions with owner + rationaleOpenAI
- LogicSkip if no decision detected
- OutputWrite each decision as a row in Notion registryNotion
What it does
Turns the back-and-forth of an email thread into a clean, searchable record of decisions. When a Front conversation is resolved or archived, this workflow reads the entire message history, identifies the concrete decisions reached (what was decided, who decided it, and the rationale), and writes each one as a row in a Notion database that the whole team can search later.
When to use it
Use it when important calls get buried in customer or vendor email threads and nobody can find "what did we actually agree to" three weeks later. Ideal for ops, partnerships, and account teams who negotiate over Front and need an auditable decision trail without manual note-taking.
How it works
- 1A Front conversation moves to archived/resolved, firing the trigger.
- 2The workflow pulls the full ordered message history for that conversation.
- 3An OpenAI model extracts a list of discrete decisions, each with a one-line summary, owner, date, and supporting quote.
- 4A filter drops the thread if no decision was detected, avoiding noise.
- 5Each decision is written as a structured page in the Notion decisions registry, linked back to the source Front conversation.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 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.