Cue works with the systems you already run
Connect Cue to your CRM, helpdesk, ecommerce platform or dealer management system. Every integration is built through workflows, so the connection matches how your business actually operates rather than a fixed template you have to work around.
How Cue integrations are built
Cue integrations run through workflows. You define the sequence: what happens in your system, what Cue sends, what gets written back.
That matters because no two setups match. Two companies both running HubSpot will have different pipelines, different properties and different rules about who owns a record. A fixed field map has to assume one of them. A workflow is built for the one in front of it.
So the systems below are examples, not limits. Workflows send HTTP requests and receive webhooks, so anything with an API can connect. Zapier and n8n cover the rest.
Popular integrations
Systems our customers connect most often
Not everything Cue connects to is listed here. If your system has an API, or the tools around it can create a workflow, it can still connect.
CRM and sales
Helpdesk and ticketing
Ecommerce
Team messaging
Automation and workflow
Messaging and delivery
AI
Finance and HR
Marketing
Data
Automotive
Pinewood AI, plus 22 further dealer management systems. See dealer management systems below.
Dealer management systems
Cue connects to 24 automotive dealer management systems, including Keyloop and Pinewood AI. Service and repair activity recorded in the DMS can trigger customer messages directly, so a customer hears about their vehicle without an advisor remembering to call.
The Keyloop integration shows what that depth looks like in practice. Repair-order events in the DMS trigger messages, and those messages carry details pulled straight from the record: vehicle registration, customer name and appointment times.
See all dealer management system integrations
Worthing Motors moved post-service follow-up from phone calls to WhatsApp. Survey engagement rose 55%, with NPS returns going from 111 in Q1 2025 to 173 in Q1 2026, which earned the dealership an additional £5,000 Stellantis rebate per quarter.
+55%
survey engagement
111 → 173
NPS survey returns, Q1 2025 to Q1 2026
£5,000
additional Stellantis rebate per quarter
For technical teams
Cue can be driven programmatically as well as through the flow builder. Teams with development resource build against the API rather than assembling flows in the interface.
Cue’s API covers authentication, inbound and outbound messaging, message templates and contact data. Webhooks push updates to your systems as they happen, and HTTP requests inside workflows let you apply your own logic to an inbound response before Cue does anything with it.
Read the developer documentation
developer.cuedesk.com
# send a message
POST /messages
{
“to”: “+44…”,
“channel”: “whatsapp”,
“template”: “service_ready”
}
# receive an update
POST your-endpoint // webhook
{ “event”: “message.replied” }
Common questions
We already have a CRM or DMS. Does Cue replace it?
No. Your CRM or DMS stays the system of record. Cue connects to it and becomes the place the customer conversation happens, with the relevant record attached.
We have been sold a shallow integration before.
Our system is not on the list.
Who does the work, and how long does it take?
Does it work across multiple sites?
