Skip to content
ActionZendeskUpdated May 2026

How do I create a Zendesk ticket from a workflow?

Short answer: Drop the "ZendeskCreate Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Subject
subject
stringRequiredSubject. Example: Cannot access my account
Description
description
stringRequiredThe initial comment/body of the ticket
Requester Email
requester_email
stringRequiredEmail of the person raising the ticket. Creates a new user if not found.
Requester Name
requester_name
stringOptionalRequester Name. e.g. "John Doe"
Priority
priority
optionsOptionalPriority. Options: Low, Normal, High, Urgent
Type
type
optionsOptionalType. Options: Problem, Incident, Question, Task
Tags
tags
stringOptionalComma-separated tags
Sample request
{
"subject": "e.g. Cannot access my account",
"description": "{{trigger.description}}",
"requester_email": "customer@example.com",
"requester_name": "John Doe",
"priority": "{{trigger.priority}}"
}
Returns
{
"ticket": {
"id": 123,
"url": "https://your.zendesk.com/api/v2/tickets/123.json",
"status": "new",
"subject": "Cannot access my account",
"priority": "normal",
"requester_id": 456
}
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Ticket.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Create Ticket.

What does the Create Ticket action do in Zendesk?
Creates a new support ticket in Zendesk with requester, subject, comment body, priority, status, type, group, assignee, and tags. The entry point for converting external alerts or forms into trackable tickets.
What inputs does Create Ticket require?
Required: Subject, Description, Requester Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Zendesk returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Create Ticket support batch operations?
Yes. Run Create Ticket inside a Loop node to process arrays. Tiny Command handles Zendesk's rate limits automatically so you don't have to throttle manually.
More actions

Other Zendesk actions.

Send create ticket from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.