WhatsApp helpdesk integration: Zendesk, Freshdesk and more

Zendesk, Freshdesk, Zoho Desk and Odoo each connect WhatsApp through Meta's Cloud API: you link a WhatsApp Business Account and the helpdesk turns one-to-one chats into tickets or conversations. None documents support for the WhatsApp groups you already run. For groups, or numbers that stay on a phone, a webhook route through n8n is the alternative.

This guide sets out what each helpdesk asks for, why group chats stay out, which n8n nodes exist for each, and how to build the webhook route without pretending it is a helpdesk channel. It is written for support and operations teams whose customers, dealers and partners message on WhatsApp as often as they email.

How do helpdesks connect to WhatsApp?

All four follow Meta's model. You need a Meta business account, which Meta now calls a business portfolio, a WhatsApp Business Account inside it, and a phone number registered to that account and verified by text or voice call. Meta reviews the display name, and until it verifies your business you work under limits: Zendesk and Freshdesk both quote 250 business-initiated conversations in a rolling 24 hours and two numbers. Both also note WhatsApp's own per-message charges on top of the helpdesk's price, and Freshworks adds 20% to what Meta bills.

What does each helpdesk need for WhatsApp?

The pattern is consistent: each channel is built for one-to-one support on a number that belongs to the helpdesk. Zoho Desk is the exception on the phone question, because it supports Meta's co-existence feature, which lets a WhatsApp Business app number stay in the app while it is connected. Even then, the app's linked devices are unlinked during onboarding and have to be linked again.

Why don't WhatsApp group chats reach the helpdesk?

Because Meta's Cloud API barely reaches groups. Its Groups API, as documented in June 2026, is open only to businesses with the badge Meta reserves for notable brands. It creates new, invite-only groups of at most 8 participants, allows one Cloud API business per group, and isn't available for WhatsApp Business app numbers. Under co-existence, Meta's feature table says group chats are not synchronised, and the chat history shared at onboarding leaves group messages out.

Zendesk says it plainly: group messages aren't supported by its WhatsApp channel. The others don't mention groups at all. So a dealer group, a housing society's committee group or a client's group with your whole account team in it stays on the phone, outside the helpdesk, unless something else carries it across.

Which n8n nodes work with these helpdesks?

n8n has nodes for three of the four, checked against its documentation on 5 October 2026:

• Zendesk: tickets (create, get, update, delete, recover a suspended ticket), users (create, search, update) and organisations, plus a Zendesk Trigger node. n8n warns that updating a ticket's tags replaces the whole list, so merge tags first.
• Freshdesk: contacts and tickets, each with create, get, get all, update and delete.
• Odoo: contacts, notes, opportunities and custom resources. Odoo's Helpdesk takes tickets from an email alias, live chat and a website form, and an operator can type /ticket in a live chat or WhatsApp conversation; from a workflow, the plainest way to open one is n8n's Send Email node, mailing the team's alias.
• Zoho Desk: no node as of October 2026; n8n's Zoho node covers Zoho CRM. Use the HTTP Request node with an OAuth2 credential to call Zoho Desk's API, which has Create Ticket and Create ticket comment calls.

WavesFlo connects to n8n through its REST API and signed webhooks, with n8n's own HTTP Request and Webhook nodes; the workflows that suit are covered in n8n workflows for WhatsApp groups.

How do I send WhatsApp chats to a helpdesk with webhooks?

This route leaves the number on the phone and copies conversations into the helpdesk. The example uses WavesFlo, which sends a signed message.received event for every inbound message on a connected number, in direct chats and groups alike, carrying the connected number it arrived on. The exception is a chat where someone has turned on WhatsApp's Restricted chat: WavesFlo connects as a linked device, so that chat stays on the phone and never reaches the helpdesk.

1. 1Link the number in WavesFlo by scanning a QR code from WhatsApp's Linked devices screen, as in connecting a number with linked devices. The phone keeps working, and needs opening at least once every 14 days to stay linked.
2. 2In n8n, start with a Webhook node that receives WavesFlo's message.received event and verifies its signature, as shown in the webhooks guide.
3. 3Add Remove Duplicates on the event ID. Delivery is at least once and order isn't guaranteed, so sort by the event's own timestamp, not by arrival.
4. 4Split direct chats from groups with a Switch node on the chat type.
5. 5For a direct chat, find the requester by phone number (Zendesk's node has a Search users operation), create them if needed, then update their open ticket or create one.
6. 6For a group, keep one open ticket per group, keyed on the group's ID, and add each message as a comment with the sender's name. A ticket per message would bury the team.
7. 7Store which ticket belongs to which chat, in a custom ticket field or a small table, so the next message lands on the same ticket.

Where do replies come from on the webhook route?

Not from the helpdesk. This route gives the helpdesk a record of each conversation; it doesn't turn the ticket into a WhatsApp reply window. Replies go out from the WavesFlo shared inbox, on the number the chat arrived on, or from the phone itself. On Growth and Enterprise, each team can let keyword replies, a chatbot and AI replies answer, or have AI draft replies for someone to check, and chats are handed on by hand or round-robin within a team, as assigning WhatsApp chats explains.

That makes the division of work plain. The helpdesk keeps history, reporting and the customer's record alongside email and calls; the inbox is where WhatsApp gets answered. If agents must reply from inside the helpdesk, with its automations and timers, use the helpdesk's own channel for one-to-one support and accept that groups stay outside it.

Which route should you choose?

• The helpdesk's own channel, for one-to-one support on a number you can move to Meta's Cloud API, or keep in the app through Zoho Desk's Co-Existence.
• The webhook route, when support happens in groups, when numbers must stay on phones, or when you run many numbers and the helpdesk only needs the record. Handling customer queries in WhatsApp groups covers working those groups day to day.
• Both side by side: a Cloud API number for public support, and linked numbers for dealer and partner groups, all logged in one helpdesk.