confirmation_numberCreate Zendesk TicketDataconfirmation_numberZendeskcreateZendeskTicket· Version 1.0.0

Files a support ticket in a connected Zendesk account, and captures the new ticket's number and link into workflow variables. Pick which Zendesk account to file in, then set the **Subject** and **Description** — both are $(variable)-interpolated, so you can carry in what the caller said earlier in the flow. Set **Requester Email** to attach the ticket to a person: Zendesk matches an existing user by that address and creates one when there is no match, so a ticket filed for a first-time caller still lands in their name. Leave it blank and the ticket is filed as the integration itself. Turn **Visible to Requester** off to file the description as an internal note your agents can see but the customer cannot. **Priority** and **Type** are optional — leave them blank to inherit the Zendesk account's own defaults. **Custom Fields** takes your Zendesk field ids and the values to write. **External ID** stores your own identifier on the ticket, which is also the handle to search on if you need to find whether a ticket was already filed for something. **Save Ticket Number To** and **Save Ticket Link To** name variables that receive the new ticket's number and its agent-facing link, so later nodes can read them back with $(name). Prerequisites: a connected Zendesk integration whose OAuth client can mint a token carrying tickets:write — filing for a requester Zendesk has to create may additionally need users:write. The flow takes the failed exit when Zendesk rejects the ticket, and default otherwise. This node can also be given to an AI agent as a tool, which is how an agent files a ticket at the end of a call; note that a ticket is not idempotent, so an agent tool call that times out may still have created one.