# Loom for AI agents. Managed auth, ready-made tools.

> Find Loom videos, read their transcripts, comment, and organize and share videos on behalf of each of your users.

- Page: https://www.agent200.com/tools/loom/
- Category: Communication
- Authentication: Managed OAuth
- Identifier in code: `loom`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Loom, through Agent200. In code: "loom".
What it does: Find Loom videos, read their transcripts, comment, and organize and share videos on behalf of each of your users.
Page: https://www.agent200.com/tools/loom/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Loom's own page, through the authorization link Agent200 returns. Never ask a user for a Loom password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: loom_list_videos, loom_get_video, loom_get_transcript, loom_list_folders. Write tools: loom_add_comment, loom_rename_video, loom_move_video, loom_share_video. Name "loom" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/loom/framework/claude/
   https://www.agent200.com/tools/loom/framework/chatgpt/
   https://www.agent200.com/tools/loom/framework/claude-code/
   https://www.agent200.com/tools/loom/framework/muse/
   https://www.agent200.com/tools/loom/framework/grok-bot/
   https://www.agent200.com/tools/loom/framework/openai-dots/
   https://www.agent200.com/tools/loom/framework/claude-duet/
   https://www.agent200.com/tools/loom/framework/hermes-agent/
   https://www.agent200.com/tools/loom/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Loom connector, your agent works with the videos of each user who connects their Loom account. It can find a video, read its transcript, comment on it, and rename, move or share it, seeing only the videos that user is allowed to view and only through the tools your project allows.

Loom is Atlassian's video messaging tool for recording and sharing screen and camera videos.

## Loom tools

- **List videos** (`loom_list_videos`, read): List the user's videos and videos shared with them.
- **Get a video** (`loom_get_video`, read): Read a video's title, owner, length and link.
- **Read a transcript** (`loom_get_transcript`, read): Read the transcript of a video.
- **List folders** (`loom_list_folders`, read): List the folders in the user's workspace.
- **Add a comment** (`loom_add_comment`, write): Leave a timestamped comment on a video.
- **Rename a video** (`loom_rename_video`, write): Change a video's title.
- **Move a video** (`loom_move_video`, write): Move a video into a folder or space.
- **Share a video** (`loom_share_video`, write): Share a video with other people.

## Limits you can set

**Turn single tools on or off.** Let the agent read videos and transcripts, and switch off `loom_share_video` so it never changes who can watch.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example reading but not organizing. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Loom

Each end user authorizes their own Loom account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Loom account, once.
const connection = await agent200
  .user("user_123")
  .connect("loom");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Loom tools

Name the user, the model and the tools. The model decides which Loom tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Summarize the Loom Sam sent about the onboarding flow",
    tools: ["loom"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, with their Atlassian account on Atlassian's own sign-in page. You never see or store their password.

**What access is requested.** Read access, and write access if the connection needs it, to the user's Loom videos. Loom's own video permissions and privacy settings still apply: the agent sees only videos the user can view.

## Example requests

- "Summarize the Loom Sam sent about the onboarding flow"
- "List the action items from my last recorded meeting"
- "Move this week's demo videos into the Sales folder"

## Guides: Loom with your AI framework

- [Loom + Claude](https://www.agent200.com/tools/loom/framework/claude.md): Connect Loom to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Loom + ChatGPT](https://www.agent200.com/tools/loom/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Loom into your own agent with OpenAI's models and the Agent200 SDK.
- [Loom + Claude Code](https://www.agent200.com/tools/loom/framework/claude-code.md): Have Claude Code build a Loom agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Loom + Muse](https://www.agent200.com/tools/loom/framework/muse.md): Connect Loom to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Loom + Grok Bot](https://www.agent200.com/tools/loom/framework/grok-bot.md): Connect Loom to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Loom + OpenAI Dots](https://www.agent200.com/tools/loom/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Loom agent with OpenAI's models and the Agent200 SDK.
- [Loom + Claude Duet](https://www.agent200.com/tools/loom/framework/claude-duet.md): Connect Loom to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Loom + Hermes Agent](https://www.agent200.com/tools/loom/framework/hermes-agent.md): Connect Loom to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Loom + OpenClaw](https://www.agent200.com/tools/loom/framework/openclaw.md): Connect Loom to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Loom OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Loom.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Loom connection, never another user's. It cannot reach anything the user or Loom has not authorized.

### Can I limit what my agent can do in Loom?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Slack](https://www.agent200.com/tools/slack.md): Search conversations and post messages in the workspaces your users connect.
- [Microsoft Teams](https://www.agent200.com/tools/microsoft-teams.md): Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.
- [Discord](https://www.agent200.com/tools/discord.md): Read channels, post messages and start threads in the Discord servers your users connect.
- [Zoom](https://www.agent200.com/tools/zoom.md): Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
