SUMMARIZATION
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.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives submitted standupHTTP webhook
- ActionFetch video transcriptLoom
- ActionWrite per-person summaryOpenAI
- LogicFind or create today's section
- OutputAppend summary to Confluence pageConfluence
What it does
This workflow turns each submitted Loom standup into a written entry on a persistent Confluence page. When someone posts their standup through your intake webhook, it transcribes the video, writes a concise summary of their update, and appends it under that day's heading on the team's standup archive page. Over time you build a searchable, permanent record of every standup in your knowledge base.
When to use it
Use this when standups flow through a custom intake (a form, a bot, or your own app) rather than directly from Loom's feed, and you want the canonical record living in Confluence alongside your other team docs.
How it works
- 1An incoming webhook fires with the Loom video URL and submitter info.
- 2The workflow fetches the transcript for that video from Loom.
- 3OpenAI writes a short, structured per-person summary (done, next, blocked).
- 4A logic step finds or creates today's dated section on the standup page.
- 5The summary is appended under that section in Confluence, preserving prior entries.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LoomVideo transcripts, libraries.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
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.
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.
Summarize the Zoom webinar Q&A and email follow-ups to attendees
After a Zoom webinar ends, extracts every question asked and its answer, builds a clean Q&A recap with timestamped jump links, and emails it to all registered attendees via Gmail.
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.