Works with what
you already use.
Dazza works with your website and app, WhatsApp and six other messaging apps, Slack, Microsoft Teams and Discord, your email, Notion, Google Drive and Confluence, your helpdesk, Shopify and your own tools. It connects to them in minutes, and your team doesn’t have to learn a new tool to look after customers.
Plugged in.
Not bolted on.
Plan tags show where a connection starts; the rest are on every plan. Each one links to its setup guide.
Your number on WhatsApp’s official Cloud API, with your approved templates after 24 hours.
Slack (answer customers)
Threads in Slack Connect channels or your internal help desk. A teammate replying in the thread takes over.
Notion
Pages and databases your team writes in, kept in sync. Toggle FAQs and database rows read well.
Google Drive
Docs, every tab of a Sheet, Slides, PDFs and Word files, from folders or one by one.
Confluence
Whole spaces or chosen pages from Confluence Cloud, re-read when they change.
Zendesk
Handovers become tickets with the whole conversation. Agents’ public replies go back to the customer; solving resolves.
Freshdesk
Tickets with the transcript and the customer’s details, and replies back to the chat after one automation rule.
HubSpot
Tickets on the contact’s record, the transcript as a note. Your team replies from HubSpot by email.
Gorgias
Tickets for your store’s team, with the transcript as an internal note and replies back to the customer.
Help Scout
Conversations in the mailbox you choose, and agents’ replies back in the chat or on WhatsApp.
Shopify
Built in: order status and tracking, stock, and cancelling or redirecting unsent orders, for the customer who ordered.
Slack alerts
Handovers, approvals and emails waiting for a reply, posted to your team’s channel with a link.
Booking and payment links
Calendly, Cal.com, a form or a payment page, filled with the details given.
Event webhooks
A signed POST when a conversation starts, is handed over or resolved, or a customer rates a chat.
REST API
Read conversations and contacts, reply as your team, resolve and add Q&As.
Llama, Mistral and more
Llama, Mistral and other models through any OpenAI-compatible provider, or your own server.
Your API.
On a short lead.
A workflow can call any web address with a signed JSON request: the details it collected, the customer’s verified email when there is one, and a timestamp. Reply with JSON and Dazza uses it in its answer.
- Signed with a secret only you and Dazza hold
- Send a test from the editor before going live
- Only runs within the rules you set
POST https://your-system.example/dazza
x-dazza-event: action.run
x-dazza-timestamp: 1792860533
x-dazza-signature: sha256=9f2c…
{
"event": "action.run",
"action": { "id": "act_…", "name": "Check an order" },
"run": { "id": "run_…", "test": false },
"inputs": { "order_number": "2048" },
"customer": {
"email": "jamie@example.com",
"verified": { "email": "jamie@example.com", "via": "code" }
},
"sentAt": "2026-10-24T10:42:00.000Z"
}// Check it came from Dazza (Node)
const expected = "sha256=" + crypto
.createHmac("sha256", process.env.DAZZA_SECRET)
.update(`${timestamp}.${rawBody}`)
.digest("hex");
// Reply with JSON. "message" is what Dazza tells the customer.
res.json({ message: "Order 2048 arrives tomorrow, 9am to 1pm." });Hear about it.
Act on it.
Event webhooks tell your systems the moment a conversation starts, is handed over or resolved, a message or a new contact arrives, or a customer rates a chat. The REST API works the other way: your code reads conversations and contacts, replies as your team on any channel, resolves conversations and adds Q&As.
- Signed with a secret for each endpoint
- Retried for about two days, with a delivery log
- 120 API requests a minute per key, on Growth and above
POST https://your-system.example/dazza-events
x-dazza-event: conversation.handed_over
x-dazza-delivery: dlv_8k2m…
x-dazza-timestamp: 1792860533
x-dazza-signature: sha256=9f2c…
{
"id": "ev_3h7q…",
"type": "conversation.handed_over",
"created_at": "2026-10-27T10:42:00.000Z",
"data": {
"conversation": {
"id": "cnv_9x2k…",
"channel": "web",
"handover": {
"reason": "customer_request",
"summary": "Sam wants to move their booking to Friday."
}
}
}
}# Reply as your team, on the conversation’s own channel
curl -X POST https://app.dazza.io/api/v1/conversations/cnv_9x2k…/reply \
-H "Authorization: Bearer dz_sk_…" \
-H "Content-Type: application/json" \
-d '{ "text": "Friday at 10 is booked for you.", "author_name": "Maya Patel" }'
# Teach Dazza an answer
curl -X POST https://app.dazza.io/api/v1/knowledge/qa \
-H "Authorization: Bearer dz_sk_…" \
-H "Content-Type: application/json" \
-d '{ "question": "Do you deliver on Saturdays?", "answer": "Yes, in London." }'Do I need Zapier to connect my systems?
No. Shopify is built in, and Zapier, Make and n8n are handy if you don’t have a developer. If you do, point a workflow straight at your own API, or use event webhooks and the REST API.
What does a workflow send?
The workflow’s name, the details it collected, the conversation and page it came from, and the customer’s email, plus whether Dazza verified it. Nothing else.
How do I know a request is really from Dazza?
Each workflow has its own secret. Dazza signs the timestamp and body with it, and you check the signature before doing anything.
Can Dazza learn from Notion, Google Docs or Confluence?
Yes, on Growth and above. Connect Notion, Google Drive or Confluence in Knowledge, pick the pages, databases, folders or spaces Dazza should read, and it keeps them in sync: only pages edited since the last check are read again, and pages you delete or stop sharing stop being used. Answers cite the original page. See Notion, Google Drive and Confluence.
Does Dazza work with Shopify and Stripe?
Yes. Shopify is built in on Growth and above: connect your shop and Dazza looks up and tracks orders, checks stock and, if you allow it, cancels or redirects unsent orders. See Connect Shopify. For Stripe, connect Stripe’s MCP server with a restricted key: see connections.
We already use Zendesk. Do we have to switch?
No. Dazza works with Zendesk, Freshdesk, HubSpot, Gorgias and Help Scout on Growth and above. It answers first, and when a customer needs a person it opens a ticket in your helpdesk with the whole conversation, who they are and why. Your agents reply there and the reply reaches the customer in the chat, on WhatsApp or by email; solving the ticket resolves the conversation. HubSpot can’t send replies back, so there your team answers by email. See Hand over to your helpdesk.
Does Dazza work with Slack?
In two ways. Dazza can answer people in Slack itself, in Slack Connect channels shared with customers or as your internal help desk, with each thread a conversation your team can take over in place. See Slack: answer customers. Separately, Slack alerts post handovers, approvals and emails waiting for a reply to one of your channels, each with a link to the conversation.
And Microsoft Teams?
Yes, through your own Azure Bot. Dazza answers in one-to-one chats and when it’s mentioned in a channel, and packages the Teams app (manifest and icons) for you to upload. See Connect Microsoft Teams.
Is there an API?
Yes, on Growth and above. The REST API reads conversations and contacts, sends team replies, resolves conversations and adds Q&As, with keys you create in Settings → Developers. Event webhooks send a signed request to your endpoint as things happen, and retry if it’s down.
Can we use our own AI model?
Yes, on Growth and above. Add your own Anthropic or OpenAI key, or any OpenAI-compatible provider, such as Groq, Together, OpenRouter or Mistral, or your own server. Your provider bills you for the model directly, and conversations count towards your plan as usual.