ActionLoomUpdated September 2026
How do I get Loom embed metadata?
Short answer: You can get loom embed info in Loom by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Loom Get Loom Embed Info action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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. |
Sample request
{"video_url": "https://www.loom.com/share/abcdef123456"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Get Loom Embed Info.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Loom Embed Info.
What does the Get Loom Embed Info action do in Loom?
Returns embed-ready metadata (iframe HTML, thumbnail, title, duration) for a Loom video URL. For "auto-embed Loom intros in blog posts" or "rich Loom previews in Slack" workflows.
What inputs does Get Loom Embed Info require?
Required: Loom Video URL. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Loom returns an error?
The run history shows the failed step with its input and the error message Loom returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Loom Embed Info support batch operations?
Run Get Loom Embed Info inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Loom's rate limits.