PROJECT MANAGEMENT
Capture a Loom handoff via webhook and create a ClickUp task with a criteria checklist
A webhook receives a Loom share event, creates a ClickUp task with the embedded Loom, and populates it with an acceptance-criteria checklist parsed from the recording's transcript.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound webhook with Loom payloadHTTP webhook
- LogicValidate Loom URL and transcript present
- ActionExtract acceptance criteria from transcriptOpenAI
- ActionCreate ClickUp task with Loom embedClickUp
- OutputWrite checklist and return task URLClickUp
What it does
Lets any tool that can call a webhook push a Loom handoff straight into ClickUp. On receiving the Loom share payload, the workflow creates a ClickUp task, embeds the recording, and fills the task with acceptance criteria extracted from the transcript, so the handoff arrives as ready-to-work scope.
When to use it
Use it when your handoff source is a custom dashboard, a Slack workflow, or a browser extension that emits a webhook rather than a native Loom trigger, and your team tracks work in ClickUp. It is the flexible glue for non-standard handoff pipelines.
How it works
- 1An inbound webhook delivers the Loom URL, title, and transcript.
- 2A logic step validates the payload has a usable Loom URL and transcript, stopping otherwise.
- 3An LLM step turns the transcript into a list of acceptance criteria.
- 4A ClickUp task is created with the Loom embedded and the title from the payload.
- 5The criteria are written to the task as a checklist and the task URL is returned in the webhook response.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
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.
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.
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.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
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.
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…
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.