SUMMARIZATION
Distill a Long Email Thread into Action Items
Pulls a tangled Gmail thread, has OpenAI extract decisions, owners, and dated next steps, then emails a clean action-item digest back.
How it runs
The automated pipeline, trigger to output.
- TriggerNew reply lands on watched Gmail threadGmail
- ActionFetch full thread and stitch chronological transcriptGmail
- LogicOpenAI extracts decisions, owners, and dated next stepsOpenAI
- ActionFormat the buckets into a readable digest
- OutputReply on the thread with the action-item digestGmail
What it does
This workflow takes a sprawling email thread — the kind with twelve replies, three forwards, and a "per my last email" buried somewhere — and turns it into a crisp list of action items. It fetches the full Gmail thread, feeds every message in chronological order to OpenAI, and asks the model to separate signal from noise: what was actually decided, who owns each follow-up, and which dates or deadlines were committed to. The result is sent back as a clean digest email so the takeaways live right next to the original conversation.
When to use it
Use it when a thread has gotten too long to safely skim and you need the "so what do I actually have to do" answer in seconds. Good fits: a vendor negotiation that spanned a week, a cross-team launch plan with shifting owners, a customer escalation thread before you reply, or a Monday-morning catch-up on a conversation that ran over the weekend. It is especially useful before forwarding a thread to someone new — they get the summary instead of scrolling through forty quoted replies.
How it works
A new message arriving on a watched Gmail label (or thread) fires the trigger. The workflow pulls every message in that thread and stitches them into a single chronological transcript with sender and timestamp on each turn. That transcript goes to OpenAI with a structured prompt that returns three buckets — Decisions made, Action items (each with an owner and a due date when one was stated), and Open questions still unresolved. The workflow formats those buckets into a readable HTML digest and sends it via Gmail as a reply on the same thread, so the action items stay attached to their source. Because it runs on Agent Hive's Sim engine, every step executes for real against your connected Gmail and OpenAI accounts — no mock nodes, no "configure later" placeholders.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 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.
