# Loom Integration: Setup, Pricing and Fixes (2026)

By Ossian Kettunen · 2026-11-22 · Source: https://www.activepieces.com/blog/loom-integration-setup-pricing-and-fixes-2026

---
<aside class="tldr"><p class="tldr-label">Summary</p><p>Three Loom integration methods exist—native connections, embeds, and automation workflows—each with different setup complexity and costs.</p><ul><li>Starter plan records maximum 25 videos before upgrade required.</li><li>Business plan costs $18 per user per month in 2026.</li><li>Six common failure causes include admin blocks and domain restrictions.</li></ul></aside>

A Loom integration's one of three things:
- a built-in connection to another app: - an embed that plays a video inside another page
- an automation connection that moves data between Loom and other tools

Start with the first two, because they're switches, not builds.

## Connect your apps with Loom

### What a Loom integration is

You will hear "integration" used for three different mechanisms. A native connection's a feature Loom ships and you enable from its own settings. An embed's a video player placed inside someone else's page.

When a trigger in Loom is wired to an action elsewhere, that's an automation connection, built in a separate tool; [Activepieces](https://www.activepieces.com) does this from an MIT-licensed core whose source is public on GitHub. Knowing which one you need tells you where to look first.

![A failed two-step workflow in Activepieces showing a Google Calendar trigger connected to a Gmail send email action, with…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/d92eb24d-50c6-4cf1-8445-b563b17f0966/lever-api-rate-limits-and-webhooks-2026-guide-sc-e97557a6.webp)

### The three routes: native, embed, automation

Read the plan column as a prompt to test before you pay. According to [Gravity](https://gravity.fast/blog/loom-pricing-explained/), Loom's Starter plan's free and Business's $18 per user per month, so an unneeded upgrade is a recurring cost.

| Route | What it does | Where you set it up | Plan needed | Time to set up |
|---|---|---|---|---|
| Native connection | Links Loom to another app so videos appear or are shared there | Loom's own settings and integrations page | Confirm on the app's listing; try Starter (free) first | A few clicks |
| Embed | Plays a Loom video inside a page, doc or message | The destination app, using a pasted Loom link | Starter (free)'s the place to test | Under a minute per video |
| Automation connection | Fires an action in another tool when something happens in Loom | A separate automation tool | Depends on which Loom trigger the tool exposes; test before moving to Business | Longest: you map each trigger and field |

The automation cost only pays off when the native route lacks the step you need.

As of 2026-11-22, when these routes were reviewed, plan names and **the $18 per user per month Business price** are as stated, per Gravity. Loom changes what each plan includes, so confirm on its pricing page before you commit.

## Steps 1 and 2: Connect Loom's native integrations

Turn on Loom's built-in integrations from inside Loom, authorize one app, and confirm it works on a real recording before you connect anything else.

### Step 1: Open Loom's integrations settings

Sign in to Loom in a browser and open your workspace settings from the menu under your profile or workspace name. Look for an Integrations entry.

Loom has moved and renamed menu items before, and I couldn't verify the exact current path, so trust the label on your screen.

You're done with this step when you can see a list of apps with a connect button next to each. If the list is missing, your account is probably not an admin on the workspace. The last subsection covers that.

![A workflow automation flow for summarizing employee feedback with scheduled trigger and AI step](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/7c25f092-fb6b-4d49-b50e-5cfa41e405ed/zapier-alternatives-with-ai-agents-best-tools-co-d55c644d.webp)

### Step 2: Authorize one app and test with a real video

Pick the single app where your team already shares videos, usually the chat tool. Click its connect button and sign in to that app when the pop-up asks.

Read the permission screen before approving it. It lists what Loom will be allowed to do in that app, and a security reviewer will ask about it later.

Then test with a real recording, not a blank one:

1. Record or open a short Loom video.
2. Paste its share link into the connected app, in a channel or document you control.
3. Check that the link expands into a preview with the title and thumbnail, instead of staying a bare URL.

If the preview expands, the connection works. A bare link means the authorization didn't finish, so disconnect and reconnect rather than adding a second app on top of a broken one.

![Activepieces workflow builder showing a test flow connecting an Every Hour schedule trigger to an Ask ChatGPT action, with…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/03467db2-7c75-4863-93ee-fa5eeacac9c2/mistral-voxtral-3-speech-models-pricing-benchmar-ffafc5ff.webp)

### Workspace admin settings that control who can connect

Whether you can authorize an app at all depends on workspace admin settings. When an admin restricts third-party apps, members see a disabled button or a request prompt.

I couldn't verify the exact setting name or which plans expose it, so check the admin area of your own workspace before you blame the integration.

Once these connections work, you'll hit their limits. A native link preview shares a video. It doesn't read a spreadsheet, ask a model to summarize the rows, and email the result on a schedule.

Look at the flow below, which is that kind of job. It has a weekly trigger, a Google Sheets read, an AI step, a Gmail send and a loop, which is what an automation tool adds.

<blockquote class="pull"><p>A native link preview shares a video. It doesn't read a spreadsheet, ask a model to summarize the rows, and email the result on a schedule.</p></blockquote>

Next up: the embeds, which need no authorization at all.

## Embed and share Loom videos

With no connection to authorize and no automation tool involved, a Loom share link or embed code puts a video into any page that accepts a URL or an iframe.

Four moves, and the video should play before you call it done:

1. Open the video in Loom and click Share.
2. Set the privacy and domain options.
3. Copy the link or the embed code.
4. Paste it into the Notion, Confluence or help center page, then load the published page and check that it plays.

### Step 3: Copy the link or embed code

You get two different things from the Share panel, and the page you are pasting into decides which one you want. The share link is a plain URL.

Notion (the team wiki and docs tool) and Confluence (Atlassian's wiki) both convert a pasted Loom URL into an inline player, so the link alone is usually enough there.

When the destination is a help center platform, or any page editor with an HTML or "embed code" block that doesn't unfurl links, you need the embed code, which is an iframe snippet.

![A help center page editor with an open embed code block, where a short iframe snippet of code has been pasted in and a…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/9b8a8f3e-2e07-44b7-8100-d5f18bd5f605/loom-integration-setup-pricing-and-fixes-2026-il-3bd0ca64.webp)

A bare link there gives the reader a blue underlined URL instead of a player.

### Step 4: Set who can view it before you paste it

Set privacy first, because an embed inherits the video's access rules rather than overriding them. If the video is limited to your workspace and you embed it in a public help center page, outside readers see a permission wall where the player should be.

![A framed video screen hung on the outside of a locked glass meeting room, facing a street; passers-by walk past with their…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/e6723158-67b9-40ea-9431-3997a6d8fc5f/loom-integration-setup-pricing-and-fixes-2026-il-8176f8fd.webp)

For a public page, the video has to be viewable by anyone with the link.

For an internal wiki, keep it restricted to people in your workspace so the embed doesn't widen access. If your plan has a domain restriction on embeds, set it to the domain that hosts the page, so the player works there and nowhere else.

After pasting, open the published page in a private browser window to see what an outside reader sees.

## Step 5: Automate Loom with a workflow tool

**Reach for a workflow tool only after the native integration and the embed fail you.** A tool adds a second account, a second bill and a second place for a recording's link to break.

![A small house with one front door, and bolted onto its side a second doorbell, a second mailbox and a second meter, all…](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/ec95ec25-499b-4b79-b395-8d3392cc56c3/loom-integration-setup-pricing-and-fixes-2026-il-22367c9a.webp)

### What Loom's own developer docs allow

Nothing on Loom's developer pages reads as a general-purpose API for managing a workspace's library. They centre on its SDK for recording and embedding videos inside your own product.

So the question for any outside tool is whether it exposes a trigger on a new video. Loom's docs alone won't give you one, so read each tool's Loom page before you build anything.

![A six-step workflow diagram showing Google Drive and Docs integration with an AI agent and conditional router.](https://ap-marketing-media.fra1.cdn.digitaloceanspaces.com/uploads/af62f771-77dc-43a9-acee-39c54feced8e/monday-automations-alternatives-best-options-in-0906d1b4.webp)

### Comparing automation tools for Loom on triggers, actions and cost

I haven't verified the trigger and action lists on these vendors' pages for this article, so this comparison leaves them out rather than guess.

It covers what each tool charges for and what its free entry point gives you. The unit matters because a workflow that fires on every recording eats the allowance at different rates.

A busy team outgrows Zapier's free plan quickly. Zapier counts tasks, one per action step, and its free plan gives 100 tasks, while a three-step workflow uses several tasks per recording, so the free plan accommodates only limited use.

Make counts credits, one per module run, and its free plan gives 1,000 credits. That's more headroom for testing, but a branching scenario spends credits on every module it touches.

Open each tool's Loom page and look for a trigger that fires on a new video.

If the page lists only actions, such as adding a video to a folder, you can't start a workflow from a recording, and that tool is out for this job.

Activepieces' 750 integrations are counted directly from the community integrations folder of its MIT-licensed open-source monorepo on GitHub, and roughly 60% of them were written by outside contributors.

If the Loom entry there lacks a new-video trigger, you can generate the missing integration with AI and add it privately to your own instance.

When a recording lands, post its share link to the team's chat channel. Follow these steps in whichever tool lists a new-video trigger.

1. Create a new workflow and pick Loom as the trigger app, then choose the new-video trigger.
2. Connect your Loom account and record a short test video so the trigger has data to pull.
3. Add a chat app as the action and choose its send-message step.
4. Map the video's title and share URL into the message body. The URL field is the one that decides whether the workflow works, so check it opens in a private window.
5. Run the test, then switch the workflow on.

If step 4 offers no share URL field, the workflow can't do this job and you should go back to the native integration.

## Loom integration errors, limits and plan costs

Before you rebuild anything, know that **six causes account for most Loom integration failures**, and none of them needs a rebuilt workflow.

The table shows each symptom with its cause and fix, and flags where the official docs say nothing, so you know which fixes are inference.

| Symptom | Cause | Fix | Docs silent? |
|---|---|---|---|
| Recording blocked at 25 videos | Starter plan cap | Delete videos or upgrade | No |
| Integration option missing or refused | Workspace admin blocked it | Ask an admin to allow it | Partly |
| Connects to the wrong workspace | Authorized while signed in to another account | Disconnect, sign in correctly, reauthorize | Yes |
| Link shows as plain text | Unfurl unsupported or video not shareable | Paste the share URL; check the video's access | Partly |
| "No access" on a video | Video is private | Change sharing to the right audience | No |
| Embed refuses to load | Domain not permitted | Allow the domain in settings | Partly |

### Plan and video limits that stop you

**At 25 videos, Starter stops**, so a team recording daily hits the wall within weeks.

You pay more per paid seat than you used to. [Pricingsaas](https://pricingsaas.com/companies/loom/diffs/2023Q3) records the Business seat at $8 per creator per month in April 2023, $12.50 in November 2023 and $15 in January 2025.

Contact support when the table says the docs are silent and the fix didn't work. That covers workspace mismatches that survive a clean reauthorization and domain blocks you can't see in settings. Send the video URL, the workspace name and the exact error text.

## What Activepieces does about this

Activepieces is the tool for the case this article keeps narrowing to: the native connection and the embed can't do the step you need, so you build one workflow. It won't replace the switches in Loom's settings, and it shouldn't.

If a link preview in your chat app covers the job, stop there and skip the second account.

Once you do need a workflow, the question is whether the tool has a Loom trigger on a new video. You can check that for Activepieces without a sales call.

The core is MIT-licensed and public on GitHub, and the 750 integrations are counted from the community integrations folder in that repository, which means anyone can verify the count.

Roughly 60% of them were written by contributors outside the company, so the ecosystem isn't entirely company-driven. Open the Loom entry there and read what it exposes before you build anything.

If it lists only actions, it can't start a workflow from a recording, and you should treat it like any other tool that fails that test.

When the entry lacks the trigger or field you need, you aren't left waiting on a vendor release. **You can generate the missing integration with AI** and add it privately to your own instance.

Because the source is open, you can also read exactly what a integration does with your Loom account before you authorize it.

That's the second thing to confirm after the new-video trigger, and the share URL field from step 4 is the one to look for.

## Frequently asked questions

### Does Loom have an API I can use?

Before you build anything that depends on pulling videos out in bulk, know that Loom has an SDK for recording and embedding, but its developer pages don't describe a general API for reading or managing your video library.

Check Loom's developer documentation and its "last updated" date first.

Only the triggers Loom exposes to them are available to automation tools.

### Is Loom's Slack integration available on the free plan?

Read plan availability off Loom's current pricing page and the Slack integration's help article, not off this article, because it changes.

The Slack connection is switched on from Loom's own integration settings, and your Slack workspace may require an admin to approve it. If the option is missing, the cause is usually plan or permissions, not a fault.

### Can I connect Loom to Google Drive or Notion without code?

For Notion, yes: pasting a Loom share link into a page turns it into an embed, with no automation involved. Google Docs and Slides accept pasted Loom links the same way.

If you want recordings copied into a specific Drive folder automatically, that's a different job, and as far as Loom's help pages describe, that's where an automation tool earns its place. Confirm the current behavior on Loom's integrations page.

### Why did my Loom integration stop working?

When a Loom integration stops working, the usual causes are a revoked permission, a connected account that left the workspace, a password or single sign-on change, or an admin restricting which apps may connect.

Start by reconnecting from Loom's integration settings, using the account that originally authorized it.

If that fails, collect the video URL, the workspace name and the exact error text, as above, and send them to support.

### How do I remove a Loom integration?

Open the integrations area in your Loom settings and disconnect the app there. Then also remove Loom from the other app's list of authorized or installed apps, such as Slack's app management page.

Disconnect on one side only and a stale authorization can stay behind. Loom's help center covers each integration's removal steps, so check the date on the page you follow.

## Related reading

- [Loom Pricing 2026: Free and Paid Plans Explained](https://www.activepieces.com/blog/loom-pricing-2026-free-and-paid-plans-explained)
- [Zendesk Native AI vs AI Agents for Support (2026)](https://www.activepieces.com/blog/zendesk-native-ai-vs-ai-agents-for-support-2026)
- [Discord Trello Integration Setup Without Code](https://www.activepieces.com/blog/discord-trello-integration-setup-without-code)

## References

- [Pricingsaas](https://pricingsaas.com/companies/loom/diffs/2023Q3)
