Zapier
Everything else Zapier reaches.
HubSpot and Pipedrive have connectors of their own. For every other tool there is a Zapier app: five triggers, four actions and one search that does the work the others get wrong.
Your CRM is not one of the two.
Plenty of teams run Zoho, Salesforce, Odoo, or a spreadsheet somebody built in 2019 and nobody is allowed to touch. Writing a connector for each is not a promise a small product should make, and “integrates with everything” usually turns out to be a landing page rather than a feature.
Five triggers
New message, new conversation, label applied, deal stage changed, new ticket. Each arrives the moment it happens, with a polling fallback for when a hook goes missing.
Four actions
Send a message, add a label, write an internal note, create a follow-up. Sending can only reply to somebody who has written to you first — it cannot open a conversation.
One search that does the real work
Find a contact by phone number, comparing digits rather than strings, so +971 50 123 4567 matches 971501234567. That match is the first step of nearly every CRM Zap, and getting it wrong is why hand-built ones quietly stop working.
Fields you can actually map
Contact name, contact number, chat labels — flat, so Zapier’s field picker offers “Contact Number” rather than a nested object nobody outside engineering can read.
A label as the routing rule
The usual shape: tag a conversation “Quote” and the label-applied trigger sends it on. Nothing leaves until somebody decides it should.
What crosses over
- Whatever your Zap carries: messages, new conversations, labels, deal stage changes and tickets.
- The contact’s name and number on every trigger, which is what the CRM on the other end matches on.
- Writes back in — a reply, a label, a note or a follow-up — from any Zap you build.
What never does
- Internal notes as a trigger. A note is stored with its own direction and every outbound path skips it.
- Private conversations. They are not visible to a token for the same reason they are not visible in the inbox.
- The message firehose unless you tick it. Every message is off by default — a busy workspace would spend tens of thousands of Zapier tasks a month on it, and that is your bill rather than ours.
Integrations are a Pro capability. Starter does not include HubSpot, Pipedrive, Zapier, webhooks or the API.
When you would use it
- Pushing a new WhatsApp enquiry into Zoho CRM or Salesforce as a lead.
- Logging every quote request into a Google Sheet the finance team already lives in.
- Posting new tickets into Slack for a team that will not open another tab.
- Creating a follow-up automatically when a deal has not moved in a week.
What this leans on
Questions people ask
Which plan is this on?
Pro. Integrations — HubSpot, Pipedrive, Zapier, webhooks and the API — are a Pro capability, and Starter does not include them.
Which CRMs does this actually reach?
Any of them that Zapier connects to — Zoho, Salesforce, Odoo, Monday, Airtable and several thousand more. There is no vendor-specific code on our side, which is exactly why the list is not ours to keep short.
Can a Zap start a conversation with somebody new?
No. Sending is reply-only: the person must have written to you first. That is a rule of the connection itself, not a setting, and it is what keeps an automation from turning into unsolicited messaging.
Will this burn through my Zapier tasks?
Not on the defaults. The conversation-level triggers fire a few dozen times a day; the every-message trigger is the expensive one and it is off until you turn it on deliberately.