Short answer: Drop the "Loom → Get Loom Embed Info" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Loom Video URL video_url | string | Required | Full public Loom share URL. |
{"video_url": "https://www.loom.com/share/abcdef123456"}
{"html": "<iframe src='https://www.loom.com/embed/abc'></iframe>","type": "video","title": "My Loom Recording","width": 640,"height": 360,"version": "1.0","author_name": "Jane Doe","provider_name": "Loom","thumbnail_url": "https://cdn.loom.com/sessions/thumbnails/abc.png"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.