Automation platforms

n8n

n8n has full support for ErzyCall's OAuth, including automatic registration — no client ID or secret to create.

Which node do I use?

Step by step

1. Add an AI Agent node, then click the + on its Tools port and pick MCP Client Tool.
2. Endpoint: https://app.erzycall.com/api/mcp
3. Server Transport: HTTP Streamable — not the deprecated SSE option.
4. Authentication: MCP OAuth2, then Create new credential.
5. In the credential, leave Use Dynamic Client Registration switched on and leave Resource URL empty. Click Connect my account and sign in to ErzyCall.
6. Back in the node, set Tools to Include. Start with Selected and pick only what the workflow needs — giving an agent all 29 tools at once makes it slower and less reliable.

Make.com

Make's MCP Client app (open beta) can connect to ErzyCall directly.

1. In a scenario, add a module from the MCP Client app.
2. Click Create a connection.
3. For MCP server, choose + New MCP server (ErzyCall isn't on Make's verified list).
4. URL: https://app.erzycall.com/api/mcp. Leave API Key / Access Token empty — ErzyCall uses OAuth.
5. Save and complete the ErzyCall sign-in.
6. Pick your module:
   • Call a tool — you choose the exact action and arguments. Deterministic and cheap. Start here to check the connection works.
   • Execute an action with AI — an LLM picks the tool from your Task description. Needs an AI provider connection and consumes credits.

Zapier

Use the MCP Client integration (beta). Don't confuse it with Zapier MCP, which is the reverse — Zapier acting as a server for other AI tools.

1. Go to your Apps page → + Add connection → search MCP Client → Add connection.
2. Fill the Connect an Account form:
   • Server URL: https://app.erzycall.com/api/mcp
   • Transport: Streamable HTTP
   • OAuth: Yes
   • Bearer Token: leave empty — it's ignored when OAuth is Yes
3. Click Yes, Continue to MCP Client, sign in to ErzyCall in the new tab, and grant access.
4. Rename the connection to something like "MCP Client — ErzyCall". Multiple MCP connections look identical in the Zap editor otherwise.
5. In a Zap, add the Run Tool action (or Run Read-Only Tool for lookups) and select the ErzyCall action you want.

REST API fallback

Some platforms can't speak MCP yet. They can still use ErzyCall through the normal REST API with an API key.

1. In the ErzyCall dashboard go to Settings → API Keys and click Create API Key.
2. Name it after the tool that will use it, and select only the scopes it needs.
3. Optionally set an expiry date. Click create and copy the key immediately — it's shown only once. It looks like ek_live_….
4. In your platform, make an HTTPS request to https://app.erzycall.com/api/v1/… with a header named X-API-Key holding that key.

curl -X GET "https://app.erzycall.com/api/v1/calls?limit=5" \
  -H "X-API-Key: ek_live_your_api_key_here"

Make.com — HTTP module

• Module: HTTP → Make a request
• Authentication type: API key → create a keychain with API key placement: In the header, parameter name: X-API-Key, Key: your ek_live_… value
• Turn Parse response on so the fields become mappable

Zapier — API by Zapier

• Action: API by Zapier → API Request (premium; stores the key in the connection rather than in each step)
• Or Webhooks by Zapier → Custom Request with header key X-API-Key and your key as the value

Full endpoint reference: ErzyCall API docs.