Evolution API icon

Evolution API

Interact with Evolution API

Actions64

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 in scenarios where you need to programmatically retrieve user profile privacy configurations from an Evolution API instance, such as integrating privacy settings into workflows or auditing user privacy preferences.

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 privacy configurations.

The node does not output binary data.

Dependencies

  • Requires an active connection to the Evolution API service.
  • Requires an API authentication credential configured in n8n (referred to generically as an API key credential).
  • The base URL for requests is set to https://doc.evolution-api.com/api-reference.
  • The node expects JSON responses and sends requests with appropriate headers (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Unsupported operation error: If the node throws an error stating that the function for the resource-operation combination is unsupported, verify that the Resource is set to "Profile" and Operation to "Fetch Privacy Settings". Also, ensure the node version supports this operation.
  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions to access the Evolution API instance.
  • Instance name issues: Providing an incorrect or empty instance name will likely cause the API call to fail. Double-check the instance name input.
  • Network or API availability: Confirm network connectivity and that the Evolution API endpoint is reachable.

Links and References

Discussion