Actions114
- Instance Actions
- Message Actions
- Group Actions
- Chat Actions
- Profile Actions
- Event Actions
- Integration Actions
- Call Actions
- Label Actions
- OpenAI Actions
- N8N Integration Actions
- EvoAI Actions
- Template Actions
- Business Actions
Profile → Update Privacy Settings
AI-generatedOverview
This node updates the privacy settings of a user's profile in the Evolution API. It allows users to control who can see their read receipts, profile picture, status, online presence, last seen, and who can add them to groups. This is useful for managing privacy preferences in messaging or social networking applications.
Use Case Examples
- A user wants to restrict their profile picture visibility to only their contacts.
- A user wants to prevent anyone from seeing their read receipts.
- A user wants to allow only specific contacts to add them to groups.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance where the profile settings will be updated. |
| Read Receipts | Controls who can see when the user has read messages. |
| Profile Picture | Controls who can see the user's profile picture. |
| Status | Controls who can see the user's status. |
| Online | Controls who can see when the user is online. |
| Last Seen | Controls who can see the user's last seen time. |
| Groups | Controls who can add the user to groups. |
Output
JSON
readreceipts- Visibility setting for read receipts.profile- Visibility setting for profile picture.status- Visibility setting for status.online- Visibility setting for online presence.last- Visibility setting for last seen time.groupadd- Visibility setting for who can add the user to groups.
Dependencies
- An API key credential for Evolution API authentication
Troubleshooting
- If the node throws an error about unsupported operation, ensure the resource is set to 'Profile' and operation to 'Update Privacy Settings'.
- Errors related to authentication usually indicate missing or invalid API credentials; verify the Evolution API credentials are correctly configured.
- Invalid or missing required parameters like 'Instance Name' can cause the node to fail; ensure all required fields are filled.