Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node interacts with the Evolution API to update privacy settings of a user profile. It allows users to configure who can see their read receipts, profile photo, status, online presence, last seen time, and who can add them to groups. This is useful for managing privacy preferences in messaging or social platforms where controlling visibility of personal information is important.
Practical examples:
- A user wants to hide their "last seen" status from everyone except their contacts.
- A user prefers that only specific contacts can see their profile photo.
- Restricting who can add the user to groups to avoid spam or unwanted invitations.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance (required string input). |
| Confirmação De Leitura | Who can see when you have read messages. Options: Todos (all), Ninguém (none). |
| Foto Do Perfil | Who can see your profile photo. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Status | Who can see your status. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Online | Who can see when you are online. Options: Todos (all), Igual Ao Visto Por Último (match last seen). |
| Visto Por Último | Who can see your last seen time. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Grupos | Who can add you to groups. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist). |
Output
The node outputs a JSON array containing the result of the privacy settings update operation. The exact structure depends on the Evolution API response but typically includes confirmation of updated settings or error details if the update failed.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
- Operation not supported error: If the selected operation or resource is not supported, the node throws an error indicating the unsupported function. Ensure the correct resource ("profile-api") and operation ("update-privacy-settings") are selected.
- API authentication errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Invalid property values: Providing unsupported option values may cause the API to reject the request. Use only the provided options for each property.
- Network issues: Connectivity problems with the Evolution API endpoint will prevent successful updates. Check network access and API availability.
Links and References
- Evolution API Documentation: https://doc.evolution-api.com/api-reference (base URL used by the node)