TestingOps.ai

MCP tools for agents · MCP tool for agents

Zapier and TestingOps: the actions you choose, for test agents

Set up a Zapier MCP server with the actions you allow, and TestingOps agents can run those actions in the apps you connected to Zapier when their work calls for it.

  • MCP tool for agents
  • Available
Request a demo Zapier MCP
Connection
MCP tool for agents
Writes back
Only after a person approves
Last checked
7 Nov 2026

In short

Zapier and TestingOps in short

The Zapier connection is an MCP tool for TestingOps agents: you create an MCP server in Zapier, add the actions agents may use and paste its token in TestingOps.

Agents can then run those actions, for example post a run summary to a team channel or add a row to a spreadsheet, without TestingOps needing a direct connection to each app.

Each successful call uses two Zapier tasks from your plan, and every action that is not marked read-only or named for reading asks for approval first.

What it does

What it does for your testing

  1. 1

    Apps without a TestingOps connection

    Input
    Actions you add to your Zapier MCP server
    TestingOps
    Agents can run them through Zapier when a task calls for it
    Output
    Work in apps TestingOps has no connection for, limited to the actions you chose
  2. 2

    A tool set you control in Zapier

    Input
    Zapier's Managed mode
    TestingOps
    Limits agents to exactly the actions you added
    Output
    No action that agents enable on their own
  3. 3

    Writes reviewed first

    Input
    An action named with send, create, update or post
    TestingOps
    TestingOps pauses the call until it is approved
    Output
    Messages and records sent through such actions only after approval

Step by step

How it works

  1. Create a Zapier MCP serverIn Zapier MCP, add an MCP server, pick Other as the AI client and name it.
  2. Add the actions agents may useAdd each action you want agents to have. Managed mode limits the agent to exactly these; Agentic mode lets it enable more on its own.
  3. Generate the token and connectOn the Connect tab, generate the token (shown once) and paste it into Zapier MCP token under Extra tools your agents may use in Integrations → API & MCP, then select Connect.
  4. Agents run actions during a taskAn agent runs a Zapier action through TestingOps; the token stays on the TestingOps server, and each successful call uses two Zapier tasks.

TestingOps classifies Zapier's actions by their annotations and by verbs in their names (create, update, send, post…); an action whose name has no such verb runs without asking, so add only the actions agents should have. Actions you add in Zapier later appear after Refresh catalog and wait in quarantine until you review them under Review tools on the connection's row.

Connect

Setup

  1. Open mcp.zapier.com and select Add MCP server.
  2. Under Choose your AI agent pick Other and name the server.
  3. Add the actions agents may use; in Settings, choose Managed mode to limit the agent to exactly these.
  4. Open the Connect tab, select Generate token and copy the token (shown once; use Rotate token if it leaks).
  5. In TestingOps, as customer admin, open Integrations → API & MCP, pick Zapier under Extra tools your agents may use (outgoing, over MCP), paste the token into Zapier MCP token and select Connect.

Documentation: Zapier MCP

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Zapier

Use cases

Use cases

Post a run summary where the team reads it

Trigger
A nightly run finishes
Uses
A message action you added in Zapier
Agent activity
Can request a post with the run's pass and fail counts; the call waits for approval
Result
A summary in the team's channel after approval
Condition
The message action must be on your Zapier MCP server

Log findings in a spreadsheet

Trigger
A team tracks test findings in a spreadsheet
Uses
A row action you added in Zapier
Agent activity
Can add a row per confirmed defect
Result
The team's sheet updated with new findings
Condition
Approval applies only if the action is marked as a write or its name contains a write verb

Tell an owner about a blocked environment

Trigger
A run cannot reach a test environment
Uses
An e-mail action you added in Zapier
Agent activity
Can request an e-mail to the environment's owner; the call waits for approval
Result
The owner is told without someone writing the e-mail by hand

Capabilities

Capabilities and limits

What is read

The actions you added to your Zapier MCP server, and what those actions return

What is produced

Results of the Zapier actions agents run; nothing is stored in TestingOps by the tool itself

Where it can write

Whatever the actions you added do in the apps connected to your Zapier account. Actions that are not marked read-only or named for reading ask first and wait for approval from someone in your organisation with Manage integrations rights (or the TestingOps team).

How it connects

Zapier's hosted MCP server (https://mcp.zapier.com/api/v1/connect) with the server's token in the Authorization header

Account and permissions

  • A Zapier account with an MCP server and the actions agents may use
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • Each successful tool call uses two Zapier tasks from your plan
  • Approval depends on the action's annotations and name; Managed mode and a short action list are the main controls
  • Up to ten live tool connections per organisation
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team wants a short message in its chat channel after every release run but has no TestingOps connection for that chat app. In Zapier it creates an MCP server in Managed mode with a single send-channel-message action and connects its token in TestingOps.

After the release run, the agent requests a message with the result counts. The call appears on the agent's task for approval, and once it is approved Zapier posts the message.

Frequently asked questions

Which apps can agents reach through Zapier?

Only the actions you add to your Zapier MCP server, in the apps connected to your Zapier account. In Managed mode agents cannot add actions themselves.

What does it cost in Zapier?

Zapier counts two tasks from your plan for each successful tool call.

Do Zapier actions need approval?

Every action that is not marked read-only or named for reading (get, list, search and similar) asks first, and someone in your organisation with Manage integrations rights (or the TestingOps team) approves it. Keep the action list short all the same.

Is this the TestingOps app inside Zapier?

No. This connection lets TestingOps agents call Zapier. Using TestingOps as a step inside your Zaps is a different thing and is not covered here.

Next step

Request a demo to see agents run a Zapier action you chose, with the approval step in between.

Request a demoMore mcp tools integrations