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
Conversation → Update Meta
AI-generatedOverview
This node operation updates the metadata of a conversation in the Crisp platform. It allows modifying user-related information such as email, nickname, phone number, avatar URL, user segments, and custom data associated with a specific conversation session. This is useful for keeping conversation details up-to-date with the latest user information, enhancing customer support and interaction tracking.
Use Case Examples
- Updating a conversation's user email and nickname after receiving updated contact information.
- Adding custom data to a conversation to track user preferences or behavior.
Properties
| Name | Meaning |
|---|---|
| Website ID | The website ID from your Crisp dashboard, identifying the website associated with the conversation. |
| Session ID | The session ID of the conversation to update metadata for. |
| User email address to update in the conversation metadata. | |
| Nickname | User nickname to update in the conversation metadata. |
| Phone | User phone number to update in the conversation metadata. |
| Avatar | User avatar URL to update in the conversation metadata. |
| Segments | User segments as a comma-separated string to update in the conversation metadata. |
| Custom Data | Custom data as a JSON object to update in the conversation metadata. |
| Additional Fields | Additional optional fields to update in the conversation metadata, such as email, first name, last name, phone, company, conversation state, blocked status, assigned user ID, operator role, domain, and verification string. |
Output
JSON
email- Updated user email address in the conversation metadata.nickname- Updated user nickname in the conversation metadata.phone- Updated user phone number in the conversation metadata.avatar- Updated user avatar URL in the conversation metadata.segments- Updated user segments as an array in the conversation metadata.data- Updated custom data as a JSON object in the conversation metadata.
Dependencies
- Crisp API with authentication credentials
Troubleshooting
- Invalid JSON in Custom Data field will cause an error; ensure the JSON is correctly formatted.
- Missing required parameters like Website ID or Session ID will cause the request to fail.
- If the API credentials are incorrect or expired, authentication errors will occur.