Connect Reachdesk MCP with Zapier

Before you start

• You'll need to log in to Reachdesk as an admin.
• You'll need a Zapier account with permission to add app connections.
• Have both Reachdesk and Zapier open in your browser. You'll switch between them a few times.

Connection steps

STEP 1

Copy your Reachdesk MCP URL

In Reachdesk, go to Settings → API & MCP. Under the Reachdesk MCP section, copy the Reachdesk MCP URL. You'll paste this into Zapier in Step 4.

Reachdesk → Settings → API & MCP

Tip: This URL is the same for every user on your Reachdesk account, so you only need to look it up once. If you can't see the API & MCP tab, ask a Reachdesk admin to enable it or generate the URL for you.

STEP 2

Start a new connection in Zapier

In Zapier, click App connections in the left-hand menu to open the Connections page, then click Create connection in the top-right corner.

Zapier → App connections → Create connection

STEP 3

Select MCP Client by Zapier

In the Add new connection window, search for "MCP" and select MCP Client by Zapier.

Add new connection: search for MCP Client by Zapier

STEP 4

Enter the connection details

Zapier will show the MCP Client by Zapier connection form. Fill it in as follows:

• Serverurl: paste the Reachdesk MCP URL you copied in Step 1
• Transport: Streamable HTTP
• OAuth: Yes
• Bearer Token: leave this blank. It isn't used when OAuth is set to Yes.

Click Connect.

MCP Client by Zapier: connection details

STEP 5

Authorize Zapier

A Reachdesk window opens asking whether to authorize Zapier MCP Integration. It lists the permissions Zapier is requesting: typically "Read" (view Reachdesk data according to your role) and "Write" (create Reachdesk objects, such as sends and campaigns, based on your role permissions). Review these, then click Authorize. You'll be redirected back to zapier.com.

Reachdesk: Authorize Zapier MCP Integration

Note: Reachdesk shows an "Unverified application" warning on this screen because Zapier MCP Integration isn't owned or operated by Reachdesk. This is expected when you start the connection from Zapier yourself.

Caution: Only click "Authorize" if you were the one who started this flow. If this screen appears unexpectedly, click "Deny" and check with your Reachdesk or Zapier admin.

STEP 6

Confirm the connection

Back on the Zapier Connections page, your new Reachdesk connection appears in the list with the app MCP Client by Zapier and the status Connected. You can now select this connection when you add an MCP Client by Zapier step to a Zap.

Zapier → Connections: Reachdesk connected

Even if a user has access to all of Reachdesk MCP's tools, they can only perform actions and view data based on their permissions and role in Reachdesk. For example, a sender role will only see their own sends, campaigns and wallets, while an admin can see everything.

Troubleshooting

I don't see the API & MCP tab in Reachdesk

This tab is role-restricted. Ask a Reachdesk admin on your team to retrieve the MCP URL or grant you access.

The Reachdesk authorization screen appeared without me starting the flow

Don't click "Authorize". Click "Deny", close the tab, and repeat the steps above from Zapier directly.

The connection doesn't reach the Reachdesk authorization screen

Check that Serverurl exactly matches the Reachdesk MCP URL from Settings → API & MCP, that Transport is set to Streamable HTTP, and that OAuth is set to Yes. Then create the connection again.

Zapier shows my Reachdesk connection as expired, or a Reachdesk step fails with an authentication error

Open Zapier → App connections, find your Reachdesk connection and reconnect it. Your session with Reachdesk may have expired.