Make

Email and calendar

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

List, run, turn on and turn off Make scenarios and review their run history on behalf of each of your users.

About Make

With the Make connector, your agent works in each user’s own Make account. It can list scenarios, run one on demand, turn scenarios on or off and check the history of recent runs, using only the tools your project allows.

Make is a visual automation platform for building workflows, called scenarios, across apps.

Tools

What your agent can do in Make.

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

  • List scenarios

    Read
    make_list_scenarios

    List the scenarios in a team and whether they are active.

  • Get a scenario

    Read
    make_get_scenario

    Get a scenario's details and schedule.

  • Run a scenario

    Write
    make_run_scenario

    Run a scenario on demand.

  • Turn on a scenario

    Write
    make_activate_scenario

    Activate a scenario so it runs on its schedule.

  • Turn off a scenario

    Write
    make_deactivate_scenario

    Deactivate a scenario so it stops running.

  • List runs

    Read
    make_list_executions

    List recent runs of a scenario and their status.

Control

Limits you can set.

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

  • Turn single tools on or off

    Let the agent read and run scenarios, and switch off make_deactivate_scenario so it can never stop one.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example scenario runs but not scenario changes. A call outside them is refused.

Get started

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

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

    Run with the Make tools

    Name the user, the model and the tools. The model decides which Make 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: "Run the lead import scenario now",
        tools: ["make"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own Make account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in Make, such as reading scenarios, running scenarios or changing their status. Users can revoke the connection later from their Make 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 Make connector and how to use it.

Agent brief
Connector: Make, through Agent200. In code: "make".
What it does: List, run, turn on and turn off Make scenarios and review their run history on behalf of each of your users.
Page: https://www.agent200.com/connectors/make/

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 Make's own page, through the authorization link Agent200 returns. Never ask a user for a Make 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: make_list_scenarios, make_get_scenario, make_list_executions. Write tools: make_run_scenario, make_activate_scenario, make_deactivate_scenario. Name "make" 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/make/framework/claude/
   https://www.agent200.com/connectors/make/framework/chatgpt/
   https://www.agent200.com/connectors/make/framework/claude-code/
   https://www.agent200.com/connectors/make/framework/muse/
   https://www.agent200.com/connectors/make/framework/grok-bot/
   https://www.agent200.com/connectors/make/framework/openai-dots/
   https://www.agent200.com/connectors/make/framework/claude-duet/
   https://www.agent200.com/connectors/make/framework/hermes-agent/
   https://www.agent200.com/connectors/make/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/make.md

Guides

Use Make with the AI you build on.

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

FAQ

Make and Agent200, answered.

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

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

Can I limit what my agent can do in Make?

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

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