Plain

Communication

Plain for AI agents. Managed auth, ready-made tools.

Read and reply to support threads, add notes, create threads and mark them done in Plain on behalf of each of your users.

About Plain

With the Plain connector, your agent works in each user’s own Plain workspace. It can list and read support threads, reply to customers, add internal notes, open new threads and mark threads as done, using only the tools your project allows.

Plain is a customer support platform for B2B teams, with threads from email, Slack and chat in one place.

Tools

What your agent can do in Plain.

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 Plain connection.

  • List threads

    Read
    plain_list_threads

    List support threads by status or customer.

  • Get a thread

    Read
    plain_get_thread

    Read a thread and its timeline.

  • Reply to a thread

    Write
    plain_reply_to_thread

    Send a reply to the customer in a thread.

  • Add a note

    Write
    plain_create_note

    Add an internal note to a thread.

  • Create a thread

    Write
    plain_create_thread

    Open a new thread for a customer.

  • Mark as done

    Write
    plain_mark_thread_done

    Mark a thread as done.

Control

Limits you can set.

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

  • Turn single tools on or off

    Let the agent read threads and add notes, and switch off plain_reply_to_thread so it can never answer a customer.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example threads but not customer replies. A call outside them is refused.

Get started

Connect Plain
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 Plain

    Each end user authorizes their own Plain 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 Plain account, once.
    const connection = await agent200
      .user("user_123")
      .connect("plain");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Plain tools

    Name the user, the model and the tools. The model decides which Plain 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: "Which support threads are waiting for a reply",
        tools: ["plain"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own Plain workspace. Each connection is their own.

  • What access is requested

    The connection acts with the permissions the user grants in Plain, such as reading threads, replying or adding notes. Users can revoke the connection later from their Plain workspace settings.

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 Plain connector and how to use it.

Agent brief
Connector: Plain, through Agent200. In code: "plain".
What it does: Read and reply to support threads, add notes, create threads and mark them done in Plain on behalf of each of your users.
Page: https://www.agent200.com/connectors/plain/

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 Plain's own page, through the authorization link Agent200 returns. Never ask a user for a Plain 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: plain_list_threads, plain_get_thread. Write tools: plain_reply_to_thread, plain_create_note, plain_create_thread, plain_mark_thread_done. Name "plain" 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/connectors/plain/framework/claude/
   https://www.agent200.com/connectors/plain/framework/chatgpt/
   https://www.agent200.com/connectors/plain/framework/claude-code/
   https://www.agent200.com/connectors/plain/framework/muse/
   https://www.agent200.com/connectors/plain/framework/grok-bot/
   https://www.agent200.com/connectors/plain/framework/openai-dots/
   https://www.agent200.com/connectors/plain/framework/claude-duet/
   https://www.agent200.com/connectors/plain/framework/hermes-agent/
   https://www.agent200.com/connectors/plain/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: /connectors/plain.md

Guides

Use Plain with the AI you build on.

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

FAQ

Plain and Agent200, answered.

Who handles the Plain 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 Plain.

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 Plain connection, never another user's. It cannot reach anything the user or Plain has not authorized.

Can I limit what my agent can do in Plain?

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 Plain.
Your agent does the rest.

Your users connect their own Plain 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)