Short answer: Drop the "Zendesk → Update User" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"userId": "{{trigger.userId}}","name": "{{trigger.name}}","email": "e.g. user@example.com","phone": "e.g. +14155551234","role": "{{trigger.role}}"}
{"user": {"id": 123,"name": "John Doe","role": "agent","email": "john@example.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.