Create User: Zendesk action

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
Name name	string	Required	Name. Example: John Doe
Email user_email	string	Required	Email. e.g. "john@example.com"
Phone phone	string	Optional	Phone. e.g. "+15551234567"
Role role	options	Optional	Role. Options: End User (customer), Agent, Admin
Email Verified verified	options	Optional	Email Verified. Options: Yes, No

Sample request

{
  "name": "e.g. John Doe",
  "user_email": "john@example.com",
  "phone": "+15551234567",
  "role": "{{trigger.role}}",
  "verified": "{{trigger.verified}}"
}

Returns

{
  "user": {
    "id": 123,
    "name": "John Doe",
    "role": "end-user",
    "email": "john@example.com"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create User.

What does the Create User action do in Zendesk?

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.

What inputs does Create User require?

Required: Name, Email. 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 Create User support batch operations?

Yes. Run Create 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