Actions253
- Platform: Account Actions
- Platform: Account User Actions
- Platform: Agent Bot Actions
- Platform: Banner Actions
- Platform: User Actions
- Account Actions
- Agent Actions
- Agent Bot (Account) Actions
- Automation Rule Actions
- Banner Message Actions
- Portal (Help Center) Actions
- Data Import Actions
- Dashboard App Actions
- CSAT Survey Response Actions
- Audit Log Actions
- Applied SLA Actions
- Reporting Event Actions
- Assignable Agents Actions
- Inbox Members Actions
- Search Actions
- Actions (contact/conversation) Actions
- Campaign Actions
- Call History Actions
- Canned Response Actions
- Chat Room Actions
- Contact Actions
- Contact Note Actions
- Conversation Actions
- Create
- Get
- List
- Send Message
- Send File
- Send with Template
- List Messages
- Delete Message
- List Attachments
- Download Attachment
- Assign Agent
- Assign Team
- Add Labels
- Remove Labels
- Update Labels
- List Labels
- Toggle Status
- Set Priority
- Add Custom Attributes
- Remove Custom Attributes
- Set Custom Attributes
- Update Last Seen
- Update Presence
- Mark Unread
- Update Attachment Metadata
- Mute
- Unmute
- Pin
- Unpin
- Send Transcript
- Filter
- Delete
- Custom Attribute Actions
- Custom Filter Actions
- Custom Resolution Reason Actions
- Custom Role Actions
- Custom Scheduled Message Type Actions
- Inbox Actions
- Integration Actions
- Label Actions
- Macro Actions
- Message Template Actions
- Notification Actions
- Profile Actions
- QuePasa Actions
- Report Actions
- Scheduled Message Actions
- SLA Policy Actions
- Team Actions
Platform: User → Update
AI-generatedSummary
Update an existing user on the platform by specifying the User ID and modifying any combination of the user's email, name, password, or custom attributes.
Inputs
- User ID (required) — The unique numeric identifier of the user to update.
- Update Fields — The fields to update for the user, including Email (string), Name (string), Password (string, password masked), and Custom Attributes as a JSON object.
Output shape
a single updated user record as returned by the platform's API
The returned data includes the updated properties of the user. The operation requires the User ID and any subset of update fields. If no fields are changed, the operation may still succeed but typically no changes will be reflected.