OtherReal-timeUpdated May 2026

Loom

Loom screen recording embed info

Loom is the screen-recording-and-sharing platform — record your screen + camera, get a shareable URL. Tiny Command exposes one action, no triggers (Loom emits view events via webhooks on paid plans): Get Embed Info (fetch embed-friendly metadata for a Loom video URL — embed HTML, thumbnail, title, duration). The connection requires no auth for public Loom videos. For workflows that need to embed Loom videos in custom destinations (blog posts auto-publishing Loom intros, Slack messages with rich Loom previews, internal docs referencing recorded walkthroughs), Get Embed Info returns the right metadata. Loom's user-facing recording happens through the desktop/browser app; programmatic recording isn't supported via this connector.

Connect Loom

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Loom can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Loom Embed Info	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.	1 fields	View →

Recipes

Pre-built Loom workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Loom → Slack alerts

AI-triage every Loom event, ping the right channel only when it matters.

Loom → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Loom → Notion database

Turn Loom into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Loom once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Loom field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Loom integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Loom to Tiny Command?

Open the Tiny Command workflow builder, drop in a Loom node, and click Connect. Authorize Loom once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Loom triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Loom today. Use Tiny Command's universal Webhook or Schedule trigger to start Loom workflows, then run any Loom action you need.

What Loom actions can I run from a workflow?

1 Loom action are available out of the box, covering other operations like "Get Loom Embed Info". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Loom integration real-time?

Loom actions execute synchronously inside your workflow. Tiny Command waits for Loom's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Loom with Tiny Command?

No. Every Loom trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Loom API endpoint directly.

How much does the Loom integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Loom integration itself has no per-app surcharge.