- Integrations
- /
- Zendesk
- /
- Actions
- /
- Update User
ActionZendeskUpdated May 2026
How do I update a Zendesk user?
Short answer: Drop the "Zendesk → Update User" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
User ID userId | string | Required | User ID |
Name name | string | Optional | Name |
Email email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Role role | options | Optional | Role. Options: End User, Agent, Admin |
Sample request
{"userId": "{{trigger.userId}}","name": "{{trigger.name}}","email": "e.g. user@example.com","phone": "e.g. +14155551234","role": "{{trigger.role}}"}
Returns
{"user": {"id": 123,"name": "John Doe","role": "agent","email": "john@example.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update User.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update User.
What does the Update User action do in Zendesk?
Updates an existing Zendesk user's name, email, role, organization, tags, or user fields. Only the fields you pass are changed.
What inputs does Update User require?
Required: User ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Zendesk returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Update User support batch operations?
Yes. Run Update User inside a Loop node to process arrays. Tiny Command handles Zendesk's rate limits automatically so you don't have to throttle manually.
More actions
Other Zendesk actions.
Action
Add Comment to Ticket
Adds a public comment (customer-visible) or internal note to an existing Zendesk ticket. Used for AI summary notes, automated status broadcasts, or piping context from external systems.
ActionCreate Organization
Creates an organization (B2B account) in Zendesk with name, domains, tags, and custom fields. Used to mirror CRM accounts into Zendesk so end-users auto-link by email domain.
ActionCreate Ticket
Creates a new support ticket in Zendesk with requester, subject, comment body, priority, status, type, group, assignee, and tags. The entry point for converting external alerts or forms into trackable tickets.
ActionCreate User
Creates a new user (customer or agent) in Zendesk with name, email, role, organization, and tags. Used to provision users before ticket creation or to mirror your auth system.
ActionDelete Ticket
Permanently deletes a Zendesk ticket by ID. Two-step: this marks it deleted; for PII purposes you may also need to "redact" comments separately.
ActionDelete User
Deletes a user from Zendesk by ID. Two-step: soft-delete first; pass permanently=true (or use the dedicated permanently-delete endpoint) for GDPR right-to-delete.
Send update user from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.