Kit

Email and calendar

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

Add and tag subscribers, manage forms and sequences, and draft broadcasts in Kit on behalf of each of your users.

About Kit

With the Kit connector, your agent works in each user’s own Kit account. It can list and add subscribers, tag them, add them to a form, list sequences and create a broadcast, using only the tools your project allows.

Kit is an email marketing platform for creators, formerly called ConvertKit.

Tools

What your agent can do in Kit.

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

  • List subscribers

    Read
    kit_list_subscribers

    List and filter subscribers.

  • Create a subscriber

    Write
    kit_create_subscriber

    Add a new subscriber.

  • List tags

    Read
    kit_list_tags

    List the tags in the account.

  • Tag a subscriber

    Write
    kit_tag_subscriber

    Add a tag to a subscriber.

  • List forms

    Read
    kit_list_forms

    List the forms and landing pages.

  • Add a subscriber to a form

    Write
    kit_add_subscriber_to_form

    Add a subscriber to a form.

  • List sequences

    Read
    kit_list_sequences

    List the email sequences.

  • Create a broadcast

    Write
    kit_create_broadcast

    Create a broadcast email as a draft or scheduled send.

Control

Limits you can set.

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

  • Turn single tools on or off

    Let the agent read subscribers and add tags, and switch off kit_create_broadcast so it can never create an email to your list.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example subscribers and tags but not broadcasts. A call outside them is refused.

Get started

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

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

    Run with the Kit tools

    Name the user, the model and the tools. The model decides which Kit 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: "How many subscribers joined through the free guide form this month",
        tools: ["kit"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Kit's own sign-in page. You never see or store their Kit password.

  • What access is requested

    The access the connection needs to their subscribers, tags, forms and broadcasts, listed on Kit's authorization screen. Users can remove the app later from their Kit account 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 Kit connector and how to use it.

Agent brief
Connector: Kit, through Agent200. In code: "kit".
What it does: Add and tag subscribers, manage forms and sequences, and draft broadcasts in Kit on behalf of each of your users.
Page: https://www.agent200.com/connectors/kit/

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 Kit's own page, through the authorization link Agent200 returns. Never ask a user for a Kit 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: kit_list_subscribers, kit_list_tags, kit_list_forms, kit_list_sequences. Write tools: kit_create_subscriber, kit_tag_subscriber, kit_add_subscriber_to_form, kit_create_broadcast. Name "kit" 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/kit/framework/claude/
   https://www.agent200.com/connectors/kit/framework/chatgpt/
   https://www.agent200.com/connectors/kit/framework/claude-code/
   https://www.agent200.com/connectors/kit/framework/muse/
   https://www.agent200.com/connectors/kit/framework/grok-bot/
   https://www.agent200.com/connectors/kit/framework/openai-dots/
   https://www.agent200.com/connectors/kit/framework/claude-duet/
   https://www.agent200.com/connectors/kit/framework/hermes-agent/
   https://www.agent200.com/connectors/kit/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/kit.md

Guides

Use Kit with the AI you build on.

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

FAQ

Kit and Agent200, answered.

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

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

Can I limit what my agent can do in Kit?

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

  • Gmail

    Gmail

    Read, search, draft and send email from each user's own Gmail account.

    Managed OAuth Email and calendar
  • Outlook

    Outlook

    Work with mail and calendar in each user's Microsoft Outlook account.

    Managed OAuth Email and calendar
  • Google Calendar

    Google Calendar

    Check availability and create, update or cancel events in your users' calendars.

    Managed OAuth Email and calendar
  • Calendly

    Calendly

    Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.

    Managed OAuth Email and calendar
200 OK

Start with Kit.
Your agent does the rest.

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