PERSONAL PRODUCTIVITY
Route Loom critique to the right ClickUp list by Figma frame
Matches feedback in a Loom design review to the specific Figma frame being discussed, then files each comment as a ClickUp task in the list owned by that frame's feature squad.
How it runs
The automated pipeline, trigger to output.
- TriggerLoom recording finished in design workspaceLoom
- ActionRead Loom transcript and linked Figma fileLoom
- ActionFetch Figma frame names to build frame indexFigma
- ActionAlign each feedback segment to a Figma frameOpenAI
- LogicRoute to owning ClickUp list (or triage if unmatched)
- OutputCreate ClickUp task with timestamp + frame linkClickUp
What it does
Long design reviews often cover several frames belonging to different squads. This workflow reads the Loom transcript, looks up which Figma frame the reviewer is referencing at each moment, and routes every piece of feedback to the ClickUp list owned by the squad responsible for that frame — so comments land in the right backlog automatically.
When to use it
When one critique video spans multiple features or pages and you don't want a human triaging which team owns each note. Ideal for design systems and multi-squad product orgs.
How it works
- 1A finished Loom recording triggers the run and its transcript plus shared Figma file link are read.
- 2The Figma file's frames and their names are fetched to build a frame index.
- 3An LLM aligns each transcript segment to the frame it most likely references.
- 4A routing branch maps each frame to its owning ClickUp list using a lookup table.
- 5A ClickUp task is created in the matched list, embedding the Loom timestamp link and the Figma frame URL.
- 6Any segment with no confident frame match is sent to a triage list for manual sorting.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect FigmaFiles, frames, comments, assets.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ClickUpDocs + tasks + chats in one workspace.
- 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 Personal Productivity workflows
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
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.