PROJECT MANAGEMENT
Compile a weekly Confluence digest of all Loom design handoffs and their ticket links
On a weekly schedule, gathers every Loom design handoff recorded that week, matches each to its Linear ticket, and publishes a single Confluence page summarizing scope and status.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList this week's Loom recordingsLoom
- LogicMatch each Loom to a Linear issueLinear
- ActionSummarize handoffs and statusesOpenAI
- OutputPublish dated Confluence digestConfluence
What it does
Produces a once-a-week rollup of design handoffs so leads can see everything that shipped to engineering in one view. It collects the week's Loom recordings, pairs each with the Linear issue it references, summarizes the criteria, and publishes a dated digest page in Confluence.
When to use it
Use it for design and engineering leads who need a regular audit of what was handed off, to whom, and whether the tickets exist. It replaces the manual Friday scramble of listing Looms and cross-checking that each has a ticket.
How it works
- 1A weekly schedule triggers the run.
- 2The week's Loom recordings are listed via the Loom integration.
- 3A logic step matches each recording to a Linear issue by key and flags any with no ticket.
- 4An LLM step writes a per-handoff summary including scope and the linked issue status.
- 5A new dated Confluence page is published with the full digest and gap flags.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect OpenAIModels, embeddings, files.
- 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 Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
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.