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 cannot see their profile photo.
- Restricting group additions to contacts only to avoid spam.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to identify which profile to update. |
| 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 message. 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 API response but generally 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 node expects the Evolution API service to be accessible.
- Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
- Operation not supported error: If the specified resource or operation is incorrect or unsupported, the node throws an error indicating the operation is not supported. Ensure the resource is "profile-api" and operation is "update-privacy-settings".
- API authentication errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Invalid property values: Providing invalid options for properties may cause the API to reject the request. Use only the allowed options as listed.
- Network issues: Connectivity problems with the Evolution API endpoint will prevent successful updates.
Links and References
- Evolution API official documentation (not provided here; consult your API provider)
- n8n documentation on creating and using API credentials
- General best practices for privacy settings management in messaging platforms