CRM Integrations

Open interfaces, so your tools and agents work from the same client record

Connect other software through a documented REST API, 16 webhook events, MCP for Claude and ChatGPT and an n8n community node. REST and MCP are on every plan, webhooks and n8n triggers on paid plans and self-hosted. From Pro, LinkedIn and email conversations sit on the client, and REST and MCP can read them.

✓ No credit card required ✓ First 14 days free

How it works

Everything your follow-up needs, in one place. Four parts that work together.

Your knowledge, your client data and your conversations live together, so every agent that helps you works from the same facts.

  1. Agents

    Every plan, Mate on paid Cloud

    Mate is built in. Or connect the AI you already pay for, and it works with the same records and rules.

  2. Inbox

    Cloud, from Pro

    Email and LinkedIn, plus WhatsApp, Instagram and Telegram, beside the client each conversation belongs to.

  3. Data

    Every plan

    Clients, deals and any list your business needs, with your own fields, stages and views.

  4. Knowledge

    Every plan

    Playbooks, prices and how you work, written once. Mate and connected agents use the pages their permissions allow.

Start from one description

One description. A workspace your agent built.

This is what setup builds from one sentence. Sample data, the real product.

  1. Describe your business

    One sentence about your team, your clients and how you sell.

  2. Mate builds it

    It asks a few questions, then creates the lists, pipeline, dashboard and playbook.

  3. Work in it

    Connect LinkedIn and email. Click through a finished example below.

Your description to Mate

We're a four-person strategy consultancy. Track clients, engagements and proposals, and help us follow up with prospects on LinkedIn.

Widgets built from the workspace's own lists and fields

Customermates for consultants

How it works

CRM Integrations in 4 steps.

  1. 01

    Create the Slack incoming webhook

    In Slack, create an app, turn on incoming webhooks, add a webhook to your workspace and pick the channel. Copy the URL and keep it secret.

  2. 02

    Add the Customermates webhook

    Under Settings → Webhooks → Add, paste the Slack URL, select Record created and choose Deals under Records from.

  3. 03

    Write the body template

    Enter {"text": "New deal: {{data.record.ref.recordId}}"}. Any path under {{data}} works as a placeholder.

  4. 04

    Test and check the log

    Create a test deal and open the Webhook log. A 2xx status code means Slack accepted it.

A CRM integration moves data or triggers between your CRM and another system, so nobody copies a deal from one screen into another. Customermates does this through four open interfaces instead of an app marketplace: a REST API, outgoing webhooks, an MCP endpoint for AI clients, and a community node for n8n. The REST API and MCP are available on every plan. Webhooks, and the n8n triggers that depend on them, come with every paid plan. Self-hosted installations have all four.

That choice has a cost you should know up front. There is no catalog of one-click apps. If you want Customermates to talk to Slack, your accounting tool or a form builder, you either point a webhook at that tool, call the API from your own code, or build the flow in an automation tool such as n8n, Make or Zapier.

What this means for follow-up. The follow-up on a client conversation often ends in another system: a message in your team chat when a reply arrives, a record in your project tool. A webhook on the messaging events, an n8n flow or your own AI client over MCP can pick that up, so the next step does not depend on someone copying it across.

The five connection types at a glance

ConnectionDirectionWhat it is forPlan
WebhooksCRM to your systemPush an event when a record in any list is created, updated, moved to Trash, restored or deleted permanently, or when an inbox message arrivesEvery paid plan and self-hosted, not Free
REST APIYour system to CRMCreate, read, search, update and delete records from code or an automation toolEvery plan, self-hosted included
MCPAI client to CRMLet Claude, ChatGPT, Cursor, Codex or Gemini CLI read and write records in conversationEvery plan, self-hosted included
n8n community nodeBothDedicated Customermates nodes in a separately run n8n instanceActions on every plan, triggers on paid plans and self-hosted; n8n is billed by n8n
Unified inboxChannels to CRMGmail, Outlook, IMAP, LinkedIn, WhatsApp, Instagram and Telegram conversations next to the record, plus read-only Google and Microsoft calendarsCustomermates Cloud, Pro or higher

Webhooks, REST and MCP come with Starter at €12 per user per month. The unified inbox starts with Pro at €29 per user per month and includes 1 connected account per user; Business includes 3 per user and shared accounts. Self-hosted installations get REST, webhooks and MCP but no inbox, so messaging events never fire there.

Which route fits which job

If you want to…UseWhy
Post a message to one Slack channel when a deal is createdA webhook with a body template, sent to a Slack incoming webhookNo automation tool needed
Hand won deals to your accounting softwaren8n, Make or Zapier on a record.updated webhook for the Deals listThose tools check the stage value and call the accounting tool's API
Create contacts from your website formThe form tool or n8n calls POST /api/v1/records/mutateCustomermates has no embeddable form of its own
Mirror records into a data warehouseWebhooks, deduplicated by event idNear real time, no polling
Ask an AI to update five deals after a callMCP from Claude, ChatGPT or another clientThe client discovers the tools and does the calls
Move a spreadsheet of existing clients inXLSX import, one list at a timeFaster than an API script for a one-off move

Webhooks

Create a webhook under Settings → Webhooks → Add, paste the receiving URL, pick events and choose the list under Records from. You can choose from 16 events: 5 record events (created, updated, moved to Trash, restored and deleted permanently, for any list you choose, your own included) and 11 messaging events, such as a received message or email and a changed calendar event.

The details that matter when you build on them:

  • Signatures. Set a secret and every delivery carries an HMAC-SHA256 signature over the request body, so the receiver can reject forged calls.
  • Retries. Timeouts, network errors, 5xx responses and 408, 425 and 429 are retried automatically, up to 10 attempts in total. Other 4xx responses are not.
  • Delivery log. Settings → Webhook log shows every delivery with status code and payload, and you can resend one from there.
  • Custom headers and body templates. Headers let you authenticate against the receiver. A body template replaces the standard JSON envelope with the shape the receiver expects, using placeholders such as {{event}} and {{data.record.ref.recordId}}.
  • Changes only. A record.updated event lists each field that changed with its before and after value, and a write that changes nothing sends no event.

Deliveries are not strictly ordered, so treat them as idempotent messages keyed by the event id and order by the payload timestamp and record version. The full catalog and payload shapes are in the webhooks documentation.

REST API

The API is versioned under /api/v1, authenticated with an x-api-key header, and described by an OpenAPI document. The same action endpoints serve every list your workspace creates and address a record by typeId and recordId: POST /api/v1/records/query and /records/search read, POST /api/v1/records/mutate creates, updates, deletes, links and unlinks, and its updateMany and deleteMany actions change up to 100 records per request. POST /api/v1/model/read returns your fields and their option IDs, which you need because the deal Stage is a configurable single choice field, not a fixed value.

An API key inherits the permissions of the user who created it. There is no per-key scope, so create keys from a user whose role fits the integration. More detail on the API feature page.

MCP for AI clients

MCP (Model Context Protocol) is an open standard for connecting AI applications to external systems. Customermates runs one MCP endpoint at /api/v1/mcp with 59 tools. Claude and ChatGPT connect as a custom connector with OAuth sign-in, as described in connecting Claude and ChatGPT. Claude Code, Codex, Cursor and Gemini CLI connect with an API key.

The client and its model are yours. Your AI provider bills its own model usage. Cloud semantic searches through MCP can still count toward Mate usage; ordinary CRM record calls do not use your client's model on the Customermates server. Messaging, calendar and social tools need a Cloud plan with the inbox. The MCP reference lists every tool.

Inside Customermates Cloud there is also Mate, the hosted assistant, which uses hosted AI credits. Mate can create and edit webhooks for you, and its routines can run a saved instruction when a record changes. That covers work that needs reading and judgment; fixed rules belong in webhooks and n8n.

n8n, Make or Zapier

None of these is bundled with Customermates. You run or subscribe to them separately, and they bring the large connector catalogs. Customermates documents the n8n patterns and publishes a community node; Make and Zapier work through their generic webhook and HTTP steps. Customermates publishes this page; the table below describes each tool's billing model from its own pricing page, checked on 8 October 2026.

ToolHow it billsFree option
n8nCloud plans by workflow executions; a whole run counts as one executionSelf-hosted Community Edition
MakeCredits; most module actions use one creditFree plan with a monthly credit allowance
ZapierTasks; each successfully completed action step counts, triggers do notFree plan, limited to two-step Zaps

n8n is fair-code under the Sustainable Use License: n8n describes its source as available and self-hostable. That is a different licence from the AGPL that covers the Customermates core.

If you already pay for one of them, use it. If you start from zero and have someone who can run a container, self-hosted n8n keeps both the CRM and the automation on your own servers. The n8n setup guide shows the webhook trigger, the HTTP Request calls and the x-api-key credential.

Slack: two routes, no native app

Customermates has no Slack app, no Slack channel in the inbox and no Slack settings screen. Slack is reachable through webhooks or n8n.

Route 1, webhook only. Slack's incoming webhooks accept a JSON POST such as {"text": "Hello"} and post it into one channel. A Customermates body template produces exactly that:

Route 2, n8n. Use n8n when the message needs logic: alert only when the deal Stage reaches a certain value, post a weekly pipeline digest from a scheduled POST /api/v1/records/query, or turn a Slack shortcut into a new contact through the API. Slack conversations never appear in the Customermates inbox either way.

What is not included

If your team needs hundreds of prebuilt, vendor-maintained connectors that a non-technical person switches on in a settings screen, a CRM with its own app marketplace fits better. Customermates fits teams that are happy to wire a webhook or let an AI client do the calls, and that want the same interfaces whether they use the cloud or self-host. ERP links follow the same pattern; the CRM and ERP integration guide walks through it.

Frequently asked questions

Keep the operating guide and source facts beside the customer record in the AI Knowledge Base.

What are CRM integrations?

Connections that move data or triggers between a CRM and other software, for example a new deal creating a project in a project tool or a form submission creating a contact. They run through an API, webhooks, an automation tool or a vendor-built connector. Customermates offers the first three plus MCP for AI clients.

Does Customermates have an open API and webhooks?

Yes: the API on every plan and in self-hosted installations, webhooks on every paid plan and when self-hosted. The REST API is documented with OpenAPI and uses an x-api-key header. Webhooks cover 16 events, with HMAC signatures, automatic retries and a delivery log.

Is there a native Slack integration?

No. Send CRM events to Slack with a webhook and body template pointed at a Slack incoming webhook, or build the flow in n8n. Creating CRM records from Slack also runs through n8n and the REST API.

Is n8n included in the subscription?

No. n8n is a separate product. You self-host the free Community Edition or subscribe to n8n's cloud. Customermates provides the community node, webhooks and API it connects to.

Can I connect Zapier or Make instead of n8n?

Yes. Any tool that can receive an HTTP POST and send HTTP requests with a custom header works. There is no dedicated Customermates app in their catalogs, so you use their generic webhook and HTTP steps.

What is the difference between an API and a CRM?

The CRM is the system that stores your contacts, deals and conversations. An API is the doorway other software uses to read and change that data. In Customermates the REST API and the MCP endpoint are two such doorways, one for programs and one for AI clients.

Is there a ready-made CommuniGator CRM integration?

Customermates does not ship a native CommuniGator connector. Its REST API and outgoing webhooks are the available integration routes; a separately built adapter must also use the other tool's supported interface. Confirm that interface and test the required objects before committing to the connection. This page does not claim a tested CommuniGator setup.

Third-party details checked on 8 October 2026 against n8n pricing, the n8n repository, Make pricing, Zapier pricing, Slack incoming webhooks and the MCP introduction.

Customermates

Send your first client event to another tool

Create an API key or a webhook during the trial and send one real CRM event, for example a new message or a changed deal, to the system that needs it.

✓ No credit card required ✓ First 14 days free