WAZI CRM INTEGRATIONS

Connect Wazi CRM to ChatGPT, Claude, Zapier, Make and n8n.
Ask your assistant about leads and tasks, or create leads from the workflows you already run.

Workspace permissions, built in.

How each Wazi integration works

Private access · MCP

ChatGPT + Wazi

CRM context, inside the conversation.

Bring CRM context into your conversation. Ask about leads and upcoming tasks without switching tabs.

You

Show my open CRM tasks due this week.

Wazi · read-only

Returns the leads and tasks you’re permitted to see in the workspace you approved.

HOW IT COMES TOGETHER

  1. 1

    Request access to the private Wazi connection. It is not yet a public ChatGPT directory app.

  2. 2

    Complete the supported ChatGPT connection setup, sign in to Wazi, and approve one CRM workspace.

  3. 3

    Ask your assistant to retrieve permitted leads and tasks. The connection is read-only.

Private access · MCP

Claude + Wazi

A grounded starting point for Claude.

Give Claude a grounded starting point, with read-only access to the CRM workspace you approve.

You

List my CRM leads and show their current stages.

Wazi · read-only

Returns the leads and tasks you’re permitted to see in the workspace you approved.

HOW IT COMES TOGETHER

  1. 1

    Request the private Claude MCP setup instructions. Availability depends on your Claude plan and connector access.

  2. 2

    Add the Wazi MCP connection using the supported setup, then sign in and select your CRM workspace.

  3. 3

    Retrieve leads and tasks for your conversation. This connection cannot edit or delete Wazi records.

Build it yourself · API

Google Gemini + Wazi

A Gemini assistant, built on your leads.

Build a Gemini-powered assistant that uses Wazi CRM leads through a custom API tool.

  1. Custom Gemini agent
  2. retrieve Wazi leads
  3. summarise stages

HOW IT COMES TOGETHER

  1. 1

    This is a developer-built Gemini API connection, not a ready-made connection inside the Gemini chat app. A complete Wazi integration has not yet been validated with Gemini.

  2. 2

    Define a function for the permitted Wazi lead operation in your Gemini API application. Your own backend executes the function call against https://api.wazi.tools/v1.

  3. 3

    Store the Wazi workspace automation key on your backend and send it as a Bearer token. Never include it in model prompts or browser code.

  4. 4

    Start with GET /leads and a sample-data test. Lead creation requires create permission and a stable Idempotency-Key. This REST path does not expose Wazi tasks or other apps.

Build it yourself · API

Microsoft Copilot + Wazi

A Copilot Studio agent, connected by API.

Explore a custom Copilot Studio agent that connects to Wazi CRM through REST API tools.

  1. Custom Copilot Studio agent
  2. look up Wazi CRM leads

HOW IT COMES TOGETHER

  1. 1

    Use Copilot Studio to build a custom agent. This is not a native Wazi app for consumer Copilot or Microsoft 365 Copilot; a complete Wazi setup has not yet been validated in Copilot Studio.

  2. 2

    Check your Copilot Studio license and environment permissions, then configure a REST API tool or custom connector for the required Wazi lead operations.

  3. 3

    Use https://api.wazi.tools/v1 as the API base. Configure a workspace automation key as the Authorization Bearer header through the platform's secure connection settings.

  4. 4

    Test with sample leads before enabling the agent. Reading leads and creating leads require the corresponding key permissions. Use stable Idempotency-Key values for create retries; Wazi tasks and other apps are not available through this REST path.

Tested · private app

Zapier + Wazi

A form comes in. A lead lands in Wazi.

Create a Wazi lead from another app, or start a workflow when a new lead arrives in your CRM.

  1. New form submission
  2. create a lead in Wazi

HOW IT COMES TOGETHER

  1. 1

    Create a workspace-scoped automation key in Wazi. Enable create access if your Zap will add leads.

  2. 2

    Use API by Zapier with Static Headers authentication: Authorization: Bearer YOUR_WAZI_KEY. Restrict the domain to api.wazi.tools.

  3. 3

    For New Item from API, GET /v1/lead-events?limit=25, use .items as the response filter and .id as the dedupe key. To create a lead, POST to /v1/leads with a stable Idempotency-Key.

  4. 4

    The private Wazi connector has passed live lead tests. Its public directory listing is pending. API by Zapier requires an eligible Zapier plan.

Build it yourself · API

Make + Wazi

Wazi CRM, inside your Make scenarios.

Add Wazi CRM to your scenarios using Make’s HTTP module and a workspace-specific API key.

  1. New enquiry
  2. Wazi lead
  3. your next workflow step

HOW IT COMES TOGETHER

  1. 1

    Create an automation key for the Wazi workspace you want to connect.

  2. 2

    Add an HTTP request in Make and store the key in a credential. Send Authorization: Bearer YOUR_WAZI_KEY.

  3. 3

    Use GET /v1/lead-events?limit=25 to poll lead events, or POST /v1/leads to create a lead. Use a stable Idempotency-Key for writes.

  4. 4

    This is API compatibility, not a native Make app. A complete Wazi scenario has not yet been validated inside Make.

Build it yourself · API

n8n + Wazi

Your own lead workflows, on your schedule.

Build your own lead workflows with n8n’s HTTP Request node, using the Wazi automation API.

  1. Schedule
  2. read new Wazi leads
  3. route to your tools

HOW IT COMES TOGETHER

  1. 1

    Create a Wazi automation key. In n8n, create a Header Auth credential with Authorization as the name and Bearer YOUR_WAZI_KEY as its value.

  2. 2

    Connect a Schedule Trigger to an HTTP Request node that calls GET /v1/lead-events?limit=25.

  3. 3

    Split out the items array and remove events already processed in previous executions, using each event’s id.

  4. 4

    To create leads, send POST /v1/leads with JSON and a stable Idempotency-Key. A complete Wazi workflow has not yet been validated inside n8n.

YOUR TOOLS, IN GOOD COMPANY

Every Wazi integration, in one place.

Compare what each integration can read and create, then open its setup steps.

Open any row for setup steps

Showing 7 integrations

What each Wazi CRM integration can read and create
PlatformTypeReads leadsReads tasksCreates leadsStatusSetup
ChatGPTAI assistantMCPYesYesNoPrivate access · MCP
ClaudeAI assistantMCPYesYesNoPrivate access · MCP
Google GeminiAI assistantREST APIYesNoYeswith create accessBuild it yourself · API
Microsoft CopilotAI assistantREST APIYesNoYeswith create accessBuild it yourself · API
ZapierAutomationREST APIYesNoYeswith create accessTested · private app
MakeAutomationREST APIYesNoYeswith create accessBuild it yourself · API
n8nAutomationREST APIYesNoYeswith create accessBuild it yourself · API
A clear starting point

Private MCP connections read CRM leads and tasks. Custom API connections read and create CRM leads. Other Wazi apps are not yet exposed through these connections.

THE BUILDING BLOCKS

Two ways to connect:
MCP and the REST API.

Two ways to connect, each with a focused purpose.
Choose the right access for the job.

FOR AI ASSISTANTS

Model Context Protocol

Let a supported AI assistant retrieve useful CRM context through Wazi’s remote MCP service.

  • Read leads and tasks
  • Sign in and approve one workspace
  • Revoke the connection in Wazi
https://mcp.wazi.tools/mcp
Private ChatGPT & Claude setupConnection information
FOR WORKFLOWS & DEVELOPERS

Automation REST API

Connect your own service or automation platform to Wazi CRM with an automation key.

  • Read leads and poll new lead events
  • Create leads with safe retries
  • Choose read or read-and-create access
https://api.wazi.tools/v1
Workspace-scoped API keysOpenAPI reference

Access you control

API keys apply to one workspace, expire after 90 days, and can be revoked.

Permissions come with you

Connections respect your active workspace membership and permitted records.

Focused AI context

MCP excludes lead contact details, notes and attachments. AI access is read-only.

FROM IDEA TO CONNECTED

How to connect Wazi
in three steps.

Create an automation key
  1. 01

    Choose what you want to connect

    An AI assistant for CRM context, or an automation tool for lead workflows.

  2. 02

    Give it the right access

    Approve an AI connection or create a workspace-specific API key. Active Wazi CRM access is required.

  3. 03

    Try a small workflow first

    Start with a sample lead or a simple question, check the result, then make it part of your day.

A LITTLE MORE CONTEXT

Wazi integration questions, answered.

Here’s what to know before connecting.

Does Wazi integrate with Zapier?

Yes, through the Wazi automation API. A private Wazi app for Zapier has passed live lead tests, but it is not yet publicly listed. Today you connect with API by Zapier and a Wazi automation key, which requires an eligible Zapier plan.

Does Wazi have an MCP server?

Yes. Wazi runs a remote Model Context Protocol service at https://mcp.wazi.tools/mcp. It gives ChatGPT and Claude read-only access to the CRM leads and tasks in one workspace you approve. Access is currently private, so request setup from Wazi.

Do I need a native Wazi app in the platform?

No. Zapier, Make and n8n can connect through their API or HTTP request tools using a Wazi automation key. The private Wazi Zapier app has passed live tests, but is not yet publicly listed. Make and n8n currently use manual API setup; complete workflows have not yet been validated in those platforms.

Can an AI assistant change my Wazi data?

The private ChatGPT and Claude MCP connections are read-only. Custom Gemini API and Copilot Studio tools use the separate REST API, which can create leads when you explicitly enable create access. These custom developer setups have not yet been validated end to end with Wazi.

Are new-lead automations instant?

The current API uses polling: your automation checks for new lead events on a schedule. Each API page contains up to 25 events. Use pagination and event-ID deduplication for larger workflows. This is not a guaranteed-delivery webhook service.

Can I connect invoices or other Wazi apps?

Not through these APIs yet. The automation API currently covers CRM leads, and MCP covers read-only CRM leads and tasks. Ask us about your use case before planning a connection to another Wazi product.

What do I need to get started?

An active Wazi CRM trial or subscription, appropriate workspace permissions, and an account with your chosen platform. Platform plans and connector access may affect availability. API keys expire after 90 days; reconnect with a new key before expiry.

Let’s connect the dots.

Have a workflow in mind? We’ll help you find the right starting point.

Talk to Wazi