Skip to main content

Zapier

Connecting a Zapier MCP server lets your agents run the Zapier actions you choose, across the apps you have connected in Zapier. You decide at Zapier exactly which actions the server exposes, and each one arrives in Outermind as its own tool.

Read How MCP Servers Work in Outermind first if you have not connected an MCP server before.

Before you start​

  • A Zapier account with the apps connected that you want agents to use. Every successful call uses Zapier tasks; see Billing notes.
  • A tenant admin in Outermind to run the wizard and grant the tools.

Zapier connects with a bearer token, not an OAuth sign-in: you create one MCP server at Zapier for Outermind and paste its connection token into the wizard.

Prepare Zapier​

  1. Go to mcp.zapier.com and create a new MCP server.
  2. When Zapier asks which client the server is for, choose Other.
  3. Set the server to managed mode, so that it exposes one tool per action you enable.
  4. Enable the actions you want agents to be able to run, and nothing else.
  5. Copy the server's connection token. Treat it like a password: anyone holding it can run the enabled actions.
warning

Use managed mode. In Zapier's default agentic mode, the server exposes a small set of general meta-tools, such as discover_zapier_actions and execute_zapier_write_action, and a single meta-tool carries out write actions in general. You would then tier and grant one general tool instead of each action, with no way to treat one action differently from another. Managed mode gives every action its own row in Outermind, its own tier and its own grant.

Connect in Outermind​

  1. Open the Capabilities hub, click MCP Servers under Tool Management, and click Add MCP server.
  2. Under Known server, pick Zapier (mcp.zapier.com). The endpoint https://mcp.zapier.com/api/v1/connect is filled in, the wizard repeats the Zapier step above, and the expected sign-in is Bearer token. Optionally edit Purpose, the one-line description agents see beside this server. Click Next.
  3. On Credential, paste the connection token into Bearer token and click Connect. Outermind stores it encrypted and never shows it again.
  4. On Summary, Outermind discovers the actions you enabled at Zapier, one tool per action, and makes them active. Under Grant tools to agents, pick an agent to choose an access level for each one; to leave an action out, use the connection page afterwards.

Zapier's MCP server works over the Streamable HTTP connection Outermind uses. Zapier's older endpoint at actions.zapier.com no longer works; always connect the mcp.zapier.com endpoint above.

Changing the actions later​

To add or remove actions, change them on your server at Zapier. Outermind's daily re-sync (or Re-sync on the connection page) picks the change up: a removed action leaves your agents at once, and a newly enabled action becomes active for your agents at once too. See Re-sync and staged operations.

If you regenerate or revoke the token at Zapier, the connection shows Needs reauth. Click Reconnect on the connection page and paste the new token.

What your agents can do​

Agents can run each action you enabled on the Zapier server, in the apps you connected at Zapier. Managed mode replaces the action allowlist Outermind's earlier built-in Zapier integration used: the list of enabled actions at Zapier is now the list.

Read actions start at tier low, and every other action starts at high. Many Zapier actions create, send or update something in another app, so expect many of them at high; see Risk tiers.

What is not available​

Nothing that Outermind's earlier built-in Zapier integration offered is missing.

Billing notes​

Zapier counts 2 Zapier tasks for every successful call an agent makes through the MCP server, against your Zapier task usage. Watch your usage after you connect, and enable only the actions agents need.