Zendesk

Manage tickets, users, and organizations with the Zendesk Support API.

Detail	Value
Category	Support
Base URL	https://{subdomain}.zendesk.com/api/v2
Authentication	Bearer Token
Endpoints	6
Connector key	zendesk

Using Zendesk in a workflow

1. Go to Connections and click New Connection.
2. Pick Zendesk from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /tickets	List tickets
POST /tickets	Create a ticket
GET /tickets/{ticket_id}	Get a ticket
PUT /tickets/{ticket_id}	Update a ticket
GET /users	List users
GET /search	Search tickets, users, organizations

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /tickets

List tickets

Detail	Value
Operation ID	support.listTickets
Method	GET
Path	/tickets

Parameters

Name	Location	Type	Required
page	query	integer	No
per_page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.listTickets.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.

POST /tickets

Create a ticket

Detail	Value
Operation ID	support.createTicket
Method	POST
Path	/tickets

Parameters

No parameters.

Request Body

Field	Type
ticket	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.createTicket.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.

GET /tickets/{ticket_id}

Get a ticket

Detail	Value
Operation ID	support.getTicket
Method	GET
Path	/tickets/{ticket_id}

Parameters

Name	Location	Type	Required
ticket_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.getTicket.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.

PUT /tickets/{ticket_id}

Update a ticket

Detail	Value
Operation ID	support.updateTicket
Method	PUT
Path	/tickets/{ticket_id}

Parameters

Name	Location	Type	Required
ticket_id	path	string	Yes

Request Body

Field	Type
ticket	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.updateTicket.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.

GET /users

List users

Detail	Value
Operation ID	support.listUsers
Method	GET
Path	/users

Parameters

Name	Location	Type	Required
page	query	integer	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.listUsers.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.

GET /search

Search tickets, users, organizations

Detail	Value
Operation ID	support.search
Method	GET
Path	/search

Parameters

Name	Location	Type	Required
query	query	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Zendesk connection from the Connection dropdown.
3. In the Operation dropdown, select support.search.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zendesk API reference.