PROJECT MANAGEMENT
Build a Notion handoff spec from a Loom walkthrough and its Figma frames
On a new Loom recording, creates a Notion handoff page that embeds the Loom, links the Figma file mentioned in the description.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom recording publishedLoom
- LogicExtract Figma URL from description
- ActionFetch Figma file and frame thumbnailsFigma
- ActionSummarize narration into criteriaOpenAI
- OutputCreate Notion handoff spec pageNotion
What it does
Assembles a single source-of-truth handoff doc in Notion. When a designer records a Loom and references a Figma file, this workflow creates a structured Notion page that embeds the video, links the exact Figma frames, and lists the acceptance criteria spoken in the walkthrough so engineers have everything in one place.
When to use it
Use it when design handoffs are scattered across Loom, Figma, and chat and engineers waste time hunting for the canonical spec. It is ideal for teams that document work in Notion and want every handoff to arrive pre-formatted.
How it works
- 1A new Loom recording triggers the flow with its transcript and description.
- 2A logic step extracts the Figma file URL from the Loom description and stops if none is present.
- 3The Figma file metadata and frame thumbnails are fetched.
- 4An LLM step turns the transcript into a titled summary plus an acceptance-criteria list.
- 5A new Notion page is created embedding the Loom, Figma links, summary, and the criteria checklist.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect FigmaFiles, frames, comments, assets.
- 3Connect NotionPages, databases, comments.
- 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.