Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Profile" and Operation "Fetch Privacy Settings," it fetches privacy-related configuration or settings associated with a user profile instance. This node is useful in scenarios where you need to programmatically retrieve privacy settings from the Evolution API, such as auditing user privacy configurations, synchronizing privacy preferences across systems, or displaying privacy settings within an application.

Example use cases:

  • Automatically fetching and displaying a user's privacy settings in a dashboard.
  • Integrating privacy settings retrieval into a workflow that manages user profiles.
  • Auditing privacy configurations for compliance purposes.

Properties

Name Meaning
Name Da Instância The name of the instance to fetch data from. This is a required string input specifying which profile instance's privacy settings to retrieve.

Output

The node outputs a JSON array containing the fetched privacy settings data for the specified profile instance. Each item in the array represents the privacy settings details returned by the Evolution API for that instance.

If the API returns binary data (not indicated here), it would be included accordingly, but based on the code and context, the output is JSON structured data representing privacy settings.

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 the Evolution API to be accessible and properly configured with valid credentials in n8n.

Troubleshooting

  • Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you select "Fetch Privacy Settings" under the "Profile" resource.
  • Authentication errors: If the API key or authentication token is missing or invalid, the node will fail to connect. Verify that the correct API credentials are configured.
  • Instance name missing or incorrect: Since the instance name is required, leaving it empty or providing an incorrect name may cause the API call to fail or return no data. Double-check the instance name input.
  • Network or API availability issues: If the Evolution API endpoint is unreachable, the node will error out. Confirm network connectivity and API service status.

Links and References

Discussion