24 native triggers
A new contact, a pipeline or deal stage change, a completed task, an inbound message and twenty more start a Zap directly, without you building a receiver.
ZAPIER INTEGRATION
Connect your CRM to everything else you use
The CRM Solid app on Zapier ships 24 triggers and 16 actions: a new contact, a deal stage change, a completed task or an inbound message can start a Zap, and a Zap can create contacts, move deals or send a Telegram or X message back. No webhook wiring and no code.
- 24 triggers
- 16 actions
- Thousands of apps
zapier.com/editor
Zap · onWhen this happens
CRM Solid · Deal stage changed to Won
Do this
1
Google Sheets
Add row to Q3 wins
2
Slack
Post to #revenue
3
QuickBooks
Create invoice
Available in the app
Triggers
- New contact
- Deal stage changed
- Task completed
- Inbound message
Actions
- Create contact
- Move deal
- Send Telegram message
- Send X message
The app is published but still private
It is not in the public Zapier directory yet. Join with the invite link and it appears in your Zap editor like any other app, with the same triggers and actions.
Join the private appTwo ways in, depending on how much you want to build
The native app is the short path. Webhooks plus the REST API is the flexible one. Both are available, and you can mix them.
16 native actions
A Zap can create a contact, move a deal, send a Telegram or X message and more, so the automation runs in both directions rather than only out of the CRM.
Connect with an API key
Authentication is a CRM Solid API key you generate in the panel. No OAuth dance, and you can revoke the key in one place if a Zap goes wrong.
Or wire it with webhooks
Prefer to control the payload? Point our outbound webhooks at a Zapier or Make catch hook and use the REST API to write back. Same events, more control.
Make works too
The webhook and API pattern is not Zapier-specific. Make, or anything that accepts an HTTP POST and can call a REST endpoint, works the same way.
Signed and revocable
Webhook deliveries are signed with HMAC-SHA256 and API keys are scoped and revocable, so an automation you no longer trust is a key you delete rather than a support ticket.
Or skip the middleman
The n8n community node and the MCP server talk to the same data. If you self-host or want an AI client driving the workspace, you do not need Zapier in the path at all.
Test before you trust
Zapier can pull sample data for each trigger, and a webhook test event verifies your side, so a Zap is verified before a real deal depends on it.
The whole workspace is reachable
Contacts, deals, tasks, messages, invoices and support tickets are all addressable, so a Zap is not limited to the handful of objects a thin integration usually exposes.
What the Zapier integration does
Zapier connects CRM Solid to thousands of other applications without code. The native CRM Solid app provides 24 triggers, events in the CRM that start a Zap, and 16 actions, things a Zap can do inside the CRM. Authentication is an API key you generate in the panel.
The usual reason to reach for it is the long tail: your accounting package, a spreadsheet the finance team lives in, an internal Slack channel, a scheduling tool. None of those justify a custom integration, and all of them are two clicks in a Zap.
Two integration patterns
Both are supported, and which one you want depends on how much control you need.
- The native app: pick CRM Solid in the Zap editor, connect with an API key, choose a trigger or action. Nothing to host, nothing to sign, and the fields come mapped.
- Webhooks plus the REST API: point an outbound webhook at a Zapier or Make catch hook for the trigger side, and call the REST API for the write side. More work, complete control over the payload.
Why it is still a private app
Zapier requires a public app to demonstrate a number of live Zaps built by unrelated users before it lists it in the directory. That is a chicken-and-egg requirement, and we are on the wrong side of it for now.
It changes nothing about how the app works. Joining through the invite link puts CRM Solid in your Zap editor exactly as a directory-listed app would be, with the same 24 triggers and 16 actions, and the same API-key connection.
What it costs
The Zapier integration is available from Pro at $24.99 a month, as is the public REST API. Outbound webhooks are a Business feature. Your Zapier plan and its task limits are between you and Zapier.
Frequently asked questions
Yes, with 24 triggers and 16 actions. It is published but still private, so it is not in the public directory: join with the invite link and it appears in your Zap editor like any other app.
Events such as a new contact, a pipeline or deal stage change, a completed task and an inbound message, among 24 in total.
Create contacts, move deals, send Telegram or X messages and more, across 16 actions, so automations can write back rather than only read.
With a CRM Solid API key you generate in the panel. There is no OAuth flow, and revoking the key immediately stops every Zap using it.
Yes. Point our outbound webhooks at a Make catch hook and call the REST API to write back. That pattern works with any tool that accepts an HTTP POST and can call a REST endpoint.
Pro at $24.99 a month, which also includes the public REST API. Outbound webhooks are a Business feature. Your Zapier subscription is separate.
Ready to ship
Wire the CRM into the rest of your stack
The Zapier integration is included from Pro. Join the app with the invite link.
Free forever plan · GDPR-ready · No credit card required