Mattering Automations Loom integration

Connect Loom to Mattering Automations to read public embed metadata (title, thumbnail, duration, iframe) for any public Loom share URL. No API key required.

Get the credential Connect Verify Node reference Troubleshooting

The Mattering Automations Loom integration does one honest thing: it reads Loom's public oEmbed endpoint. Give the loom.get_oembed node a public Loom share URL and it returns the embeddable iframe HTML, the thumbnail URL and dimensions, the video width and height, the title, and the duration.

There is no credential to set up. Loom does not offer an open or authenticated REST API, so this connector cannot list videos, read folders, or manage recordings. The one public endpoint Loom publishes is oEmbed, and that is exactly what the node wraps.

Before you start

A Mattering workspace with access to the Automations app.
A public Loom share URL to read (private or unlisted videos are not accessible).

No credential needed

Loom's oEmbed endpoint is public. There is no API key, no OAuth, and no account to connect, because Loom does not offer an open API.

This connector uses Loom's public oEmbed endpoint, so it needs no API key and no secret. You add the connector and the node is ready to use.

There is nothing to copy or paste; skip straight to connecting the node in the next step.

Connect Loom to Mattering

In Mattering Automations, open Connectors and click Add Connector.

Choose Loom from the list.

There is no credential to enter, so click Connect. The Loom: Get Video oEmbed node appears in your canvas palette.

Verify it works

Open an automation canvas and drop Loom: Get Video oEmbed onto it. Set url to any public Loom share URL and run a test step: a successful response returns the title, thumbnail URL, duration, dimensions, and the embed iframe HTML. A private or unlisted URL returns a 404, which the node reports as a handled failure.

Node reference

1 node, generated from the connector itself so this reference always matches what ships.

Read and query nodes 1

Loom: Get Video oEmbed

loom.get_oembed

Fetch oEmbed metadata for a PUBLIC Loom share URL. Returns the embeddable iframe HTML, thumbnail URL and dimensions, video width and height, title, and duration. Public endpoint (no auth). Private or unlisted videos return a 404. Verified live 2026-07-24.

Using the integration

On the automation canvas

When a workflow receives a Loom share URL, resolve it to a title, thumbnail, and duration so a downstream step can render a real preview or write clean metadata into a Mattering database. Use maxwidth and maxheight to size the embed iframe.

Validate a link is public

A 404 from the node means the URL is private, unlisted, or broken. Branch on the failure to catch bad links before they reach an audience, instead of shipping a dead embed.

From AI assistants over MCP

The node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can turn a bare Loom link into structured metadata before acting on it.

Troubleshooting

The node returns a 404 for a video you can watch

oEmbed only serves public videos. If the recording is private or unlisted, the endpoint returns a 404 even when you can view it while signed in. Change the video's visibility to public, or use a public share link.

You expected a node to list your Loom videos

No such node exists, and none can. Loom does not offer an open or authenticated REST API, so listing videos, reading folders, or managing recordings is not possible from any automation. This integration reads public embed metadata for a URL you supply.

The embed comes back larger than you want

Pass the optional maxwidth and maxheight parameters. Loom clamps the iframe and thumbnail to fit while preserving the aspect ratio, so set the size the destination needs.

The Loom MCP

What connecting Loom unlocks for AI agents and automations, with common uses and FAQs.

More guides

All Automations documentation

Every integration guide, plus how connectors, credentials, and workflows fit together.

Loom is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.