Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Profile" and Operation "Fetch Privacy Settings," it fetches privacy settings data from a specified instance of the Evolution API. This node is useful when you want to programmatically retrieve user profile privacy configurations from an Evolution API instance, for example, to audit privacy settings or synchronize them with other systems.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance from which to fetch the privacy settings. This is a required string input. |
Output
The output of the node is a JSON array containing the fetched privacy settings data from the specified Evolution API instance. Each item in the array represents a structured object corresponding to the privacy settings retrieved. The exact structure depends on the Evolution API response but generally includes fields related to user profile privacy configurations.
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 set to
https://doc.evolution-api.com/api-reference. - The node expects JSON responses and sends JSON content-type headers.
- Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node will throw an error stating that the function for the given resource-operation combination is not supported. Ensure you use valid resource and operation names.
- Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly configured.
- Instance Name missing or incorrect: Since "Instance Name" is required, leaving it empty or providing an incorrect instance name may cause the API call to fail or return no data.
- Network or API endpoint issues: Connectivity problems or changes in the Evolution API endpoint could cause failures. Check network access and API availability.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on creating custom nodes