Will a re-sent webhook create duplicate requests?

No — requests are deduplicated on workspace + Zendesk ticket id, so a retried or replayed delivery for the same ticket doesn't create a second row.

Do I have to configure the ARR field?

No, it's optional. Without it, the request is still created — the ARR badge simply doesn't populate on the matched customer record.

No — Zendesk is a Business-tier integration.

Ticket creation. Zendesk's `ticket.created` event is what creates the Customer Request.

Support · Available now

Every new Zendesk ticket becomes a Customer Request, deduplicated against the source ticket so re-deliveries and retries never create a second copy.

Zendesk integration in short

The Zendesk integration connects Zendesk with Planoda — available now.
Every new Zendesk ticket becomes a Customer Request, deduplicated against the source ticket so re-deliveries and retries never create a second copy.
What you can do: Create a Customer Request from a new Zendesk ticket, keyed on workspace + ticket id so the same ticket is never ingested twice. Carry the requesting organization's ARR onto the matched customer record, when your Zendesk trigger is configured to send it, so the right-rail ARR badge reflects real account value.
Connect it from Settings → Integrations in a few steps — no code required.

What you can do

Create a Customer Request from a new Zendesk ticket, keyed on workspace + ticket id so the same ticket is never ingested twice.
Carry the requesting organization's ARR onto the matched customer record, when your Zendesk trigger is configured to send it, so the right-rail ARR badge reflects real account value.
Preserve the ticket subject, description, and requester so the request has real context, not just a link.
Route the ticket into the same Customer Requests queue as every other support-channel source, so triage doesn't require checking multiple tools.

Great for

Route support tickets into the same triage queue engineering already works from.
Weight incoming requests by account ARR so high-value customers' tickets don't get lost in volume.

Setup

Connect ZendeskFrom Settings → Integrations, choose Zendesk and authorize Planoda to receive ticket webhooks.
Send ARR (optional)In Zendesk Admin → Triggers, configure the ticket-created trigger's JSON body to include the organization's `arr_usd` custom field if you want the ARR badge populated.
Watch requests arriveThe next new ticket appears as a Customer Request with its subject and description carried over.
Triage from PlanodaLink the request to an issue, prioritize it, and track it through resolution alongside every other request source.

FAQ

Works with

Where this fits

Ready to connect?