# Zendesk + Krokul CRM

Yes. Krokul CRM integrates with Zendesk Support. Client companies and contacts match Zendesk organizations and users, and every Zendesk ticket appears in the client card and feed in Krokul with its status and priority. The link runs through the Krokul app in Zapier, Make, n8n and Albato, or through the Krokul API and webhooks.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### Support knows the client from the first ticket

A client company added in Krokul becomes an Organization in Zendesk, and its contacts become Users of that organization. When an agent edits an email or phone in Zendesk, the Krokul contact follows. The first Ticket from a new client already shows the right organization.

### Zendesk tickets inside the client card

Each Ticket from a matched user appears in the Krokul client card as a linked record with the number, subject, status, priority and a link to Zendesk. New tickets and status changes also go to the client feed. Before a renewal call, the account manager sees open problems without asking support.

### A solved Zendesk ticket updates its Krokul record

When the ticket status becomes solved in Zendesk, the linked Krokul record turns `resolved` and the feed notes who solved it. Krokul reports on tickets per client company read those records, so churn reviews include the tickets each client opened.

### Won deals mark paying clients in Zendesk

A won deal adds a tag to the Organization in Zendesk, such as the name of the plan the client bought. Zendesk triggers and views can then route tickets from paying clients to the right group.

## What moves between Zendesk and Krokul

| Zendesk Support | Krokul | Direction | When |
|---|---|---|---|
| Organization | Client company | Krokul ↔ Zendesk | A company is created or changed in either system |
| User | Contact | Krokul ↔ Zendesk | A person is created or changed in either system |
| Ticket | Linked ticket in the client card | Zendesk → Krokul | A ticket is created by a matched user |
| Ticket status and priority | Ticket status and a note in the feed | Zendesk → Krokul | The ticket status changes |
| Organization tag | Won deal | Krokul → Zendesk | A deal reaches a won stage |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with an API key.
2. Pair the Krokul trigger Company Created or Contact Created with the Zendesk action Find or Create Organization or Find or Create User.
3. From Zendesk, start with New Ticket or Updated Ticket and use a Krokul search for the contact by email, then the action Create Ticket or Create Comment.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for client companies, contacts and tickets.
2. Subscribe a Krokul webhook to clientCompany.created and contact.created, verify the x-crm-signature header, create the Organization or User through the Zendesk API and keep its Zendesk ID on the Krokul record with externalRef/api-upsert.
3. Point a Zendesk webhook for ticket.created at your receiver. It finds the requester with contact/api-find and opens the matching Krokul ticket with ticket/api-create.
4. On ticket.status_changed, the receiver calls ticket/api-update so the Krokul ticket shows the same status as Zendesk.

**Triggers:** New Ticket; Updated Ticket; New Comment on Ticket; New Ticket in View; New Organization; New User.

**Actions:** Find or Create Organization; Find or Create User; Create Ticket; Update Ticket; Add Tag(s) to Ticket; Find Tickets.

### For integrators

Zendesk webhooks subscribe to event types such as `zen:event-type:ticket.created` and `zen:event-type:ticket.status_changed`, and each request carries `X-Zendesk-Webhook-Signature` with a timestamp header for an HMAC check. In Krokul, a receiver writes through the public REST API and stores the Zendesk ticket ID as an external key on the Krokul ticket. Krokul adds signed webhooks, a delivery log and a sandbox company.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Zendesk?

Yes. Krokul integrates with Zendesk Support through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.

### Can the account manager see Zendesk tickets in Krokul?

Yes. Tickets appear in the client card and the feed with number, subject, status, priority and a link. The full conversation stays in Zendesk.

### Krokul has its own tickets with SLA. Do I need both?

Answer clients in one place. Teams on Zendesk keep replies and SLA there, and Krokul shows the same tickets beside deals. Teams without a help desk use Krokul tickets directly.

### Which records sync both ways?

Organizations with client companies, and users with contacts. Tickets come from Zendesk into Krokul.

## Limits

Agents answer clients in Zendesk, and the conversation, macros and SLA policies stay there. Krokul shows the ticket list next to deals and invoices, so sales and support look at the same client.

## Related services

- [Freshdesk](https://krokul.com/en/integrations/freshdesk/index.md)
- [Intercom](https://krokul.com/en/integrations/intercom/index.md)
- [Jira](https://krokul.com/en/integrations/jira/index.md)
- [Slack](https://krokul.com/en/integrations/slack/index.md)
- [Gmail](https://krokul.com/en/integrations/gmail/index.md)

[Customer support](https://krokul.com/en/integrations/category/help-desk/index.md)

Zendesk is a trademark of Zendesk, Inc. Krokul is not affiliated with Zendesk.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs