Loom

Communication

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.

About Loom

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.

Tools

What your agent can do in Loom.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Loom connection.

  • List videos

    Read
    loom_list_videos

    List the user's videos and videos shared with them.

  • Get a video

    Read
    loom_get_video

    Read a video's title, owner, length and link.

  • Read a transcript

    Read
    loom_get_transcript

    Read the transcript of a video.

  • List folders

    Read
    loom_list_folders

    List the folders in the user's workspace.

  • Add a comment

    Write
    loom_add_comment

    Leave a timestamped comment on a video.

  • Rename a video

    Write
    loom_rename_video

    Change a video's title.

  • Move a video

    Write
    loom_move_video

    Move a video into a folder or space.

  • Share a video

    Write
    loom_share_video

    Share a video with other people.

Control

Limits you can set.

You decide what your agent may do in Loom, and Agent200 runs every call within those limits.

  • 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

Connect Loom
in three steps.

  1. 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.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 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.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // 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);
    }
  3. 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.

    run.js
    Conceptual example
    Run a request with the connector's tools
    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);

Access

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.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Loom connector and how to use it.

Agent brief
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/

This page is also available as Markdown, for agents and LLMs: /tools/loom.md

Guides

Use Loom with the AI you build on.

Step-by-step setup for Loom with a specific model, assistant or agent framework.

FAQ

Loom and Agent200, answered.

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.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Discord

    Discord

    Read channels, post messages and start threads in the Discord servers your users connect.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
200 OK

Start with Loom.
Your agent does the rest.

Your users connect their own Loom accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)