Slack Integration, Built on Webhooks and Your Own n8n

What This Page Does and Does Not Claim

Customermates does not ship a Slack integration. There is no Slack app to install, no Slack settings screen in the product, and no Slack option in the connected-accounts list. The unified inbox covers email, LinkedIn, WhatsApp, Instagram, and Telegram; Slack is not one of its channels.

What Customermates does ship is the machinery an external automation tool needs to talk to Slack on your behalf: outbound webhooks on 26 record and messaging events, a versioned REST API, and an MCP endpoint. Wire those to n8n, Make, or Zapier, add that tool's Slack node, and you get the behavior described below. The Slack side runs in your automation tool, not in Customermates.

We would rather write that down than let the page imply a product we have not built.

What You Need

• A Customermates workspace on any tier. Webhooks and the REST API are available from Starter.
• An automation tool that can receive an HTTP request and post to Slack. n8n is the one we document, self-hosted or on n8n's own cloud. It is a separate product with its own pricing; nothing about it is bundled with a Customermates subscription.
• A Slack workspace where you can authorize that tool.

CRM-to-Slack Notifications

The pattern is always the same: Customermates fires a webhook, your automation tool receives it, formats a message, and posts it to Slack. Create the webhook under Company → Webhooks → New and choose the events you care about. The payload shape is documented at Webhooks.

Deal change notifications. Subscribe to deal.created and deal.updated and post to a channel when a deal changes. Deal stage is a single-select custom column rather than a fixed product field, so your workflow reads the column value from the payload and branches on it — which also means you can alert on any custom column, not only stage.

New lead alerts. Subscribe to contact.created and notify the team the moment a record lands. Include the fields you care about and a link back to the record.

Pipeline summary reports. Webhooks are event-driven, so a digest is a scheduled job in your automation tool: run on a cron, call GET /api/v1/deals, aggregate, post the summary. The REST API is documented in the OpenAPI spec.

Messaging alerts. Subscribe to messaging.message.received or messaging.email.received to route new inbound conversations into Slack. These events require a messaging tier.

Slack-to-CRM Actions

The reverse direction runs through the REST API or MCP, again driven by your automation tool.

Create records from Slack. A Slack shortcut or slash command triggers your workflow, which calls POST /api/v1/contacts with an x-api-key header. The same pattern works for organizations, deals, services, and tasks.

Update records from Slack. PATCH the record. Relations are a separate concern: they change only through the dedicated links endpoint and the manage_record_links MCP tool, never through a plain field update.

Log notes from Slack. Post the Slack message body onto the record's notes through the API or the update_record_notes MCP tool.

Let an agent do it. Instead of hand-building each call, point an MCP-speaking agent at /api/v1/mcp and let it interpret the Slack message. That is the same 46-tool surface Claude, ChatGPT, and Gemini use.

What This Is Not

It is not a one-click install. You are building and maintaining workflows in a separate tool. That is real setup work, and it is honest to say so.

It is not included in your subscription. Customermates does not resell, host, or bundle n8n. If your automation tool costs money, that cost is yours.

It is not a Slack inbox. Slack conversations do not appear in the unified inbox and are not stored as CRM messages. What you get is notifications out and API calls in.

Nothing is rate-limit-free. Slack, your automation tool, and the Customermates API each apply their own limits. See messaging rate limits for the parts we control.

Why Build It This Way

No lock-in to one integration. The same webhook and REST surface that drives Slack drives Microsoft Teams, Discord, a data warehouse, or an internal service. We did not have to ship a Slack integration for you to have one.

You control the signal. Which events fire, which channels receive them, and what each message contains are decisions in your workflow, not toggles we guessed at.

The core is inspectable. The AGPL core CRM, webhook payloads, REST contract, and MCP tool definitions are in the repository. Self-hosting runs the core application and PostgreSQL under Starter entitlements; Slack and n8n remain external.

Frequently Asked Questions

Does Customermates have a native Slack integration? No. There is no Slack app, no Slack channel in the unified inbox, and no Slack screen in the product. Everything on this page is built with an external automation tool against the webhook and REST surfaces.

Is n8n included with Customermates? No. n8n is a separate open-source product. You self-host it or subscribe to n8n's cloud. Customermates publishes a community node for it and documents the integration patterns, and that is the extent of the relationship.

Can I use Zapier or Make instead? Yes. Nothing in the webhook or REST surface is n8n-specific. Any tool that can receive an HTTP POST and call an HTTP API will work.

Which events can I subscribe to? 26 events across records and messaging. The full list is at Webhooks.

Can I post CRM data into Slack without writing code? Yes, in the sense that n8n, Make, and Zapier are visual builders. You still design the workflow yourself; there is no preconfigured Customermates-to-Slack template shipped by us.

Will there ever be a native Slack integration? It is not on the roadmap as a committed item, and we will not list it here until it exists.

Get Started

Read Webhooks for the event payloads and n8n for the wiring patterns. Create a webhook in Company → Webhooks, point it at your automation tool, add the Slack node, and send your first deal.updated message into a channel. From there, everything else on this page is the same pattern with different events.