ActionZendeskUpdated September 2026

How do I update a Zendesk user?

Short answer: You can update user in Zendesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zendesk Update User action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Update User in Zendesk — start free All 17 Zendesk actions

Update User in Zendesk — start free

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.

Google Sheets → Zendesk

2 Google Sheets triggers

HubSpot → Zendesk

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Zendesk returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Update User support batch operations?

Run Update User inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Zendesk's rate limits.

More actions