Actions64
- Website Actions
- Conversation Actions
- People Actions
- Operator Actions
- Settings Actions
- Analytics Actions
- Availability Actions
- Campaign Actions
- Helpdesk Actions
- Visitors Actions
- Batch Actions
- Verify Actions
Operator → Change Membership
AI-generatedOverview
This node operation allows changing the membership role of an operator in a Crisp website. It is useful for managing operator permissions and roles within the Crisp platform, such as upgrading an operator to an administrator or changing their role to a member. For example, an admin can use this operation to update the role of a support agent to an administrator to grant them higher privileges.
Use Case Examples
- Change an operator's role from member to administrator to grant additional permissions.
- Downgrade an operator's role to member to restrict access.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the Crisp website where the operator belongs. |
| User ID | The user ID of the operator whose membership role is to be changed. |
| Additional Fields | Collection of optional fields including the new role to assign to the operator. |
Output
JSON
role- The updated role of the operator after the membership change.userId- The user ID of the operator whose membership was changed.
Dependencies
- Crisp API with API key credentials
Troubleshooting
- Ensure the Website ID and User ID are correct and correspond to existing entities in Crisp.
- Verify that the API credentials have sufficient permissions to change operator roles.
- Common errors include authorization failures or invalid user IDs, which can be resolved by checking credentials and input values.
Links
- Crisp API - Change Operator Membership - Official Crisp API documentation for changing an operator's membership role.