Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows users to interact with the Evolution API, specifically providing functionality to update privacy settings of a user profile. This operation is useful for managing who can see various aspects of your profile such as read receipts, profile picture, status, online presence, last seen time, and group addition permissions.
Typical use cases include:
- Automating privacy configuration updates across multiple accounts or instances.
- Integrating privacy setting changes into broader workflows that manage user profiles.
- Quickly adjusting visibility settings in response to policy changes or user preferences.
For example, you could set the profile picture visibility to "My Contacts" while allowing "Everyone" to see your online status, all through an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance where the profile exists; required to identify the target instance. |
| Read Confirmation | Who can see when you have read messages. Options: Everyone, Nobody. |
| Profile Picture | Who can see your profile picture. Options: Everyone, My Contacts, Except Specific Contacts, Nobody. |
| Status | Who can see your status message. Options: Everyone, My Contacts, Except Specific Contacts, Nobody. |
| Online | Who can see when you are online. Options: Everyone, Same as Last Seen. |
| Last Seen | Who can see your last access time. Options: Everyone, My Contacts, Except Specific Contacts, Nobody. |
| Groups | Who can add you to groups. Options: Everyone, My Contacts, Except Specific Contacts. |
Output
The node outputs a JSON array containing the result of the privacy settings update operation. Each item in the output array corresponds to the response from the Evolution API after applying the requested privacy settings. The exact structure depends on the API response but generally confirms success or failure of the update.
No binary data output is indicated by the source code.
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. - The node expects JSON content-type headers for requests and responses.
- Proper configuration of the API credential within n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you select valid combinations of resource and operation.
- Authentication errors: If the API key or credentials are missing or invalid, the API calls will fail. Verify that the API key credential is correctly configured.
- Invalid property values: Providing invalid options for privacy settings may cause the API to reject the request. Use only the allowed option values as specified.
- Network issues: Connectivity problems to the Evolution API endpoint will cause failures. Check network access and proxy settings if applicable.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on creating custom nodes for further customization guidance.