DocumentationWorkflowsApps and services
Zendesk node
Manage Zendesk support tickets right from your workflow: create tickets, list them, and add comments. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
8 min readUpdated
What this node does
Manage Zendesk support tickets right from your workflow: create tickets, list them, and add comments.
Use Zendesk as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add Zendesk from the node catalog.
- 02Complete the required fields and map values from previous steps.
- 03Run the node with a small test record and inspect its output.
- 04Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- Create ticket
- List tickets
- Add comment
Settings
| Field | Meaning | Area |
|---|---|---|
| Zendesk credentials | Select your Zendesk connection from Secrets. Subdomain, agent email, and API token are stored securely there in separate, clearly labelled fields. | Protected |
| Action | Choices: Create ticket, List tickets, Add comment | Standard |
| Subject | The title of the new ticket. | Standard |
| Message | The text of the first ticket comment, or the new comment. | Standard |
| Requester email | Optional: email address of the person the ticket is created for. | Standard |
| Priority | Optional: priority of the new ticket. | Standard |
| Sort by | Optional: field to sort the ticket list by. | Standard |
| Sort order | Choices: Ascending, Descending | Standard |
| Per page | How many tickets to load per page (max 100). | Standard |
| Page | Optional: page number for pagination. | Standard |
| Ticket ID | The ID of the ticket to add the comment to. | Standard |
| Publicly visible | When on, the customer sees the comment. When off, it's an internal note. | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
Example and test run
Create a support ticket from a contact form: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"action": "create_ticket",
"subject": "Frage zur Rechnung Nr. 10234",
"comment_body": "Der Kunde hat eine Frage zur Rechnung vom Juni und bittet um Rückruf.",
"requester_email": "kunde@example.com",
"priority": "normal"
}Access and security
Before activation, review which data enters this step and what its output contains.
Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.