Zendesk

Open a new Zendesk ticket with subject, body, requester, assignee, priority, and custom field values in one call.

Permanently remove a Zendesk end-user record by ID, typically for GDPR erasure or test data cleanup.

Permanently delete a ticket by ID — use for deduplication, test cleanup, or removing spam tickets that slipped past filters.

Create a new Zendesk organization record with name, domain mapping, and custom fields so all tickets from that domain are automatically grouped.

Fetch full details of a single Zendesk ticket by ID — status, assignee, tags, custom fields, and description.

Strip one or more tags from a Zendesk ticket — useful for clearing routing or workflow tags once a stage is complete.

Retrieve a paginated list of all tickets in the account, optionally filtered by status, with full ticket objects for bulk processing.

Create a new Zendesk ticket via the general endpoint — equivalent to 'Create a ticket' but exposed as a separate integration node for workflow branching.

Restore a suspended ticket back to the normal ticket queue, making it visible and actionable to your support team.

Upload a file attachment to an existing Zendesk ticket — logs, screenshots, contracts, or any binary blob become part of the ticket record.

Modify any writable field on an existing ticket — status, assignee, priority, tags, subject, or custom fields.

Post a public or internal comment to an existing Zendesk ticket — the agent can reply on behalf of the team or leave private notes for agents.

Retrieve the definition and configuration of a single custom or system ticket field by ID, including its type, options, and display name.

Append one or more tags to a ticket's tag list without overwriting existing tags — safe for multi-system tagging workflows.

Return the complete schema of every ticket field in the account — system defaults and all custom fields — so the agent can map field IDs dynamically.

Update an existing Zendesk organization's name, domain, tags, or custom fields — typically used when account details change upstream.

Create a new end-user or agent record in Zendesk with name, email, role, organization, and custom profile fields.

Modify ticket fields via the general endpoint — used in workflow branches where the ticket node originates from a General resource context.

Permanently delete a Zendesk user record — irreversible, so typically triggered by a verified deletion pipeline.

Update a Zendesk user's profile fields — name, email, role, organization, phone, and custom attributes — via the general node.

Fetch a single Zendesk user record by ID — profile, role, organization memberships, and custom fields.

Create a Zendesk user via the general endpoint — functionally identical to 'Create a user' but available as a separate node for branched workflow logic.

Return a paginated list of all Zendesk users — end-users and agents — for bulk inspection, reporting, or migration.

Return all Zendesk organizations a given user belongs to — useful when a user spans multiple accounts or franchises.

Fires when a new agent group is created in Zendesk, enabling the agent to provision downstream resources for that group immediately.

Fires whenever a new tag is applied to any Zendesk ticket, letting the agent react to tagging events as routing or escalation signals.

Fires when a ticket enters a specific saved Zendesk view — scoped by view ID — so the agent reacts only to tickets that match that view's filters.

Fires the moment any new ticket is created in Zendesk — the broadest ticket trigger, ideal for intake workflows that run on every inbound request.

Fires via webhook when a tag is applied to a Zendesk user record, enabling the agent to react to user-level classification events like VIP tagging or opt-out marking.

Fires when a new organization is created in Zendesk, enabling the agent to immediately wire up downstream provisioning for the new account.

Fires whenever a ticket lands in the Zendesk suspended queue — typically spam or unverified senders — so the agent can triage without human eyes on the queue.

Fires whenever a defined action occurs on a ticket — such as a comment added, status changed, or tag applied — providing a finer-grained event feed than 'Updated Ticket'.

Fires whenever any field on a ticket is updated — status, assignee, priority, tags, or custom fields — the most general ticket-update trigger.

Fires when a ticket that belongs to a specific saved Zendesk view is updated — scoped reaction so only updates in a particular queue trigger the agent.