Search Tickets
zendesk.search_tickets
ActionBusiness appsconnection required
Calls the Zendesk API GET /api/v2/search.json.
Search Zendesk tickets (type:ticket is enforced).
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Zendesk
- Secret shape
- {"email", "api_token"}
- Config it needs
- subdomain
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
query Search query, e.g. 'status:open requester:a@b.co'. | string | Yes | — | — | — |
limit Max tickets (1-100). | number | No | 25 | ≥ 1 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"limit": 25
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
tickets | array | — |
count | number | — |
total | number | — |
{
"count": 0,
"tickets": [],
"total": 0
}Related Zendesk nodes
Solutions with Zendesk
See Search Tickets run in a workflow.
In a technical demo we add the Zendesk connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.