Integrations · WhatsApp
Connect WhatsApp to KudosCRM.
Through the REST API or a webhook step, with a WhatsApp Business provider. Here is exactly what works today, what you need from Meta first, and what is still in development.
The short answer
KudosCRM connects to WhatsApp through its API today: a WhatsApp Business provider (Gupshup, Interakt, Twilio or similar), or a Zapier or Make workflow, sends new conversations into Kudos CRM as leads and updates contacts and deals, using a personal access token and KudosCRM's inbound endpoint and outbound webhooks. You need a Meta-verified business, a provider account, and approved message templates. A native WhatsApp inbox inside KudosCRM is in development and is not part of the product yet.
How it works
Three things, in this order.
1. Get a WhatsApp Business provider
An ordinary WhatsApp or WhatsApp Business app account cannot be automated. You need the WhatsApp Business Platform — either directly on Meta’s Cloud API or through a Business Solution Provider such as Gupshup, Interakt, Twilio, AiSensy or Wati — a Meta business account, and a phone number registered as a WhatsApp sender. Outbound messages sent outside the 24-hour customer-service window must use message templates Meta has approved in advance. Meta bills per message delivered (it replaced conversation-based pricing on 1 July 2025), and your provider adds its own fee; those charges are theirs, not ours.
2. Create a KudosCRM personal access token
In KudosCRM, generate a personal access token with write scope. The provider (or a Zapier or Make workflow that sits between) uses it as a Bearer token to call the REST API: create or update a contact when a new WhatsApp number writes in, create a deal when a conversation turns into an enquiry, log the exchange as an activity. The API reference lives at app.kudoscrm.com/docs.
3. Wire the two directions
Inbound: point the provider's message webhook at a KudosCRM inbound endpoint (a published inbound form URL that accepts any JSON), so every first message from a new number becomes a lead with the phone number attached, routed like any other lead. Outbound: subscribe the provider, or your Zapier step, to KudosCRM's signed webhooks — deal stage changes, new tasks, contact updates — and send an approved template message back.
Works today
What you can do now
- New WhatsApp enquiries land as leads with the phone number, source and first message, and follow your routing rules
- Contacts and deals created or updated from a WhatsApp conversation by the provider or a no-code step
- Each exchange logged as an activity on the contact's timeline
- Signed outbound webhooks on contact, deal, task and import events so your provider can send approved template messages
- Personal access tokens with read-only or write scopes, revocable at any time
Rolling out
What is not there yet
- A WhatsApp inbox inside KudosCRM where agents read and reply next to the contact record (in development, not in the product yet)
- WhatsApp as a step in KudosCRM workflows and sequences
- Media (images, documents) received from WhatsApp shown inline on the record
Early access to the native WhatsApp inbox
Leave your work email. We write once, when it opens.
Honest scope
If native WhatsApp is the deciding factor
Some CRMs sold in India message customers on WhatsApp Business from inside the product today, and if that is the one thing you are buying a CRM for, they are ahead of us on it right now. What KudosCRM gives you instead is the rest of the stack in one plan (pipeline, ticketing, forms, booking, live chat) and an API that any WhatsApp provider can talk to, so the connection is yours to keep regardless of which provider you use.
See how the two approaches compare for an Indian team on our KudosCRM vs Zoho CRM in India page.
FAQ
Frequently Asked Questions
Start free today
Build the WhatsApp connection during your trial.
14 days of Pro free, no card. Personal access tokens, the inbound endpoint and webhooks are all there on day one.