Zendesk n8n integrationAutomate Zendesk with n8n.

Opens a ticket in Zendesk from data already in the workflow, and returns the created ticket with its ID for the nodes that follow.

• Description: the first comment on the ticket, and the only required field. It usually comes from the incoming item, for example {{ $json.message }}.
• Subject: in Additional Fields, optional for the API but the line agents scan in the queue.
• Type: Question, Incident, Problem or Task, which drives how the ticket gets triaged.
• Group Name or ID: the group the ticket is assigned to, from the list or an expression.

Erases a ticket permanently. Zendesk keeps regular and suspended tickets in separate places, so the node asks which pile to look in before it removes anything.

• Ticket Type: Regular or Suspended. Picking the wrong one returns nothing to delete rather than deleting the wrong ticket.
• Ticket ID: the numeric identifier, not the subject, often carried over as {{ $json.id }}.

Reads one ticket and hands back its full payload: status, requester, group, tags and custom field values, all available to later nodes as JSON.

• Ticket Type: Regular for the live queue, Suspended to inspect something held back before deciding what to do with it.
• Ticket ID: the identifier of the ticket to read, typically the one the trigger just delivered.

Lists tickets in bulk and supports Zendesk search syntax, which makes it the reporting workhorse of the node.

• Ticket Type: required, and it changes the whole result set.
• Return All: on, n8n walks every page of results; off, Limit caps how many tickets come back.
• Query: in Options, the Zendesk search string that narrows the list.
• Status and Group Name or ID: filter to one state or one team.
• Sort By and Sort Order: order by Created At, Priority, Status, Ticket Type or Updated At, ascending or descending.

Brings a suspended ticket back into the normal queue, where it behaves like any other ticket and can be assigned, replied to and closed.

• Suspended Ticket ID: the identifier from the suspended list, which is not the ID the ticket will carry once it is live.

Applies changes to a ticket that already exists, from a one word status change to a public reply written by another node.

• Ticket ID: required, the ticket being modified.
• Public Reply: the answer the requester sees. Internal Note stays between agents and accepts HTML.
• Status: New, Open, Pending, On-Hold, Solved or Closed.
• Assignee Email: hands the ticket to an agent by email address.
• Tag Names or IDs: careful, Zendesk replaces the entire tag list, so any tag missing from the update is removed. Read the ticket first and merge, or add tags through HTTP Request.

Returns the definition of a single ticket field: its title, type and, for dropdowns, the option values Zendesk accepts.

• Ticket Field ID: the numeric identifier of the field, visible in the Zendesk admin URL for that field.

Lists both system and custom ticket fields in one call, which is the fastest way to discover what a Zendesk instance actually stores on a ticket.

• Return All: on for the complete catalog of fields; off, Limit stops after the first few.

Adds a person to Zendesk, as an end user, an agent or an admin, and returns the user record with the ID used everywhere else.

• Name: the only required field, the display name of the user.
• Email: the primary address, in Additional Fields, and the value Zendesk matches inbound mail against.
• Role: End User, Agent or Admin.
• Organization Name or ID: the default organization for this user.
• Verified: on, Zendesk treats the identity as confirmed and skips the verification email.

Removes a user from Zendesk. Their tickets stay, but the profile disappears, so this belongs at the end of a workflow rather than in the middle of one.

• User ID: the numeric identifier of the profile, taken from a previous search rather than typed by hand.

Reads one profile and returns the whole record: role, organization, tags, locale, notes and custom user fields.

• User ID: the identifier of the profile to read, usually {{ $json.requester_id }} pulled from a ticket.

Lists the users of the account, with a filter on role when only part of the directory is needed.

• Return All: on to page through the entire directory; off, Limit sets the ceiling.
• Roles: in Filters, keep End User, Agent, Admin or any combination of the three.

Returns the organizations a person belongs to. Zendesk allows several memberships per user, and this operation is the one that shows all of them rather than just the default.

• User ID: the profile whose memberships are listed.

Hands back the counters Zendesk keeps about a person, the related data around the profile rather than the profile itself.

• User ID: the profile to inspect.

Finds people without knowing their Zendesk ID, which is what most workflows actually have to work with.

• Query: in Filters, free text matched against the directory, typically an email address.
• External ID: the identifier from your own system, if it was stored on the profile at creation.
• Return All and Limit: control how many matches come back, useful when a query is broader than expected.

Rewrites fields on an existing profile, one at a time or in a batch, and returns the updated record.

• User ID: required, the profile being edited.
• Email, Phone, Name: the contact details, in Update Fields.
• Organization Name or ID: moves the person to another account.
• Role and Ticket Restriction: change what the person can do, and which tickets they see, among Organization, Groups, Assigned and Requested.
• Suspended: on, the user cannot sign in and their tickets get suspended too.

Returns how many organizations the account holds, as a single number rather than a list. It is the cheapest call in the node, since nothing is paged and nothing is filtered.

Registers a company in Zendesk and returns it with its ID, ready to be attached to users and tickets.

• Name: required, and the label agents search on.
• Domain Names: comma separated domains. Zendesk uses them to attach new contacts to this organization automatically.
• Details and Notes: the address and any context agents should read before replying.
• Tag Names or IDs: tags applied to the organization, from the list or by ID.

Drops an organization from the account. Members are not deleted with it, they simply end up without a company attached, and their tickets stay where they are.

• Organization ID: the numeric identifier of the record to remove, which the workflow should read from a previous node rather than hold as a constant.

Reads one company record and returns everything stored on it: domains, notes, tags and custom organization fields.

• Organization ID: the identifier of the record to read, often coming from user.getOrganizations earlier in the workflow.

Lists the companies in the account, which is how an external system gets a full picture of the Zendesk client base.

• Return All: on, every page of organizations is retrieved; off, Limit decides where the list stops.

Returns the related data Zendesk keeps around a company rather than the company record itself, which is what you want when the question is about activity instead of contact details.

• Organization ID: the company to inspect, usually resolved earlier in the run from the requester attached to a ticket.

Edits a company record in place, which keeps tickets and memberships attached while the details change.

• Organization ID: required, the record being edited.
• Name: in Update Fields, for a rebrand or a fixed typo.
• Domain Names: the comma separated list of domains, worth updating when a company adds a second one.
• Notes and Details: context agents read before replying.
• Tag Names or IDs: the tags carried by the organization.