Get Ticket

zammad.get_ticket
ActionBusiness appsconnection required

Calls the Zammad API with the connection's credentials.

Read one ticket by its numeric id.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Zammad
Secret shape
the API token, or {"api_token": "…"}
Config it needs
base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
ticket_id
The ticket to act on, as its numeric Zammad id (not the ticket number).
stringYes——12
expand
Ask Zammad to resolve the association ids into names alongside them.
booleanNofalse——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "expand": false,
  "ticket_id": "12"
}

Output

One shape.

result

FieldTypeExample
id
The ticket's numeric id.
number—
number
The ticket number people quote, such as '67001'.
string—
title
The ticket's title.
string—
group_id
Id of the group the ticket is routed to.
number—
state_id
Id of the ticket's state.
number—
priority_id
Id of the ticket's priority.
number—
owner_id
Id of the agent the ticket is assigned to.
number—
customer_id
Id of the customer the ticket belongs to.
number—
organization_id
Id of the customer's organization.
number—
created_at
When the ticket was opened, as an ISO 8601 stamp.
string—
updated_at
When the ticket last changed, as an ISO 8601 stamp.
string—
article_ids
Ids of the articles on the ticket.
array—
{
  "article_ids": [],
  "created_at": "",
  "customer_id": 0,
  "group_id": 0,
  "id": 0,
  "number": "",
  "organization_id": 0,
  "owner_id": 0,
  "priority_id": 0,
  "state_id": 0,
  "title": "",
  "updated_at": ""
}

See Get Ticket run in a workflow.

In a technical demo we add the Zammad connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.