Short answer: Drop the "Zendesk → Create Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Subject subject | string | Required | Subject. Example: Cannot access my account |
Description description | string | Required | The initial comment/body of the ticket |
Requester Email requester_email | string | Required | Email of the person raising the ticket. Creates a new user if not found. |
Requester Name requester_name | string | Optional | Requester Name. e.g. "John Doe" |
Priority priority | options | Optional | Priority. Options: Low, Normal, High, Urgent |
Type type | options | Optional | Type. Options: Problem, Incident, Question, Task |
Tags tags | string | Optional | Comma-separated tags |
{"subject": "e.g. Cannot access my account","description": "{{trigger.description}}","requester_email": "customer@example.com","requester_name": "John Doe","priority": "{{trigger.priority}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.