Evolution API icon

Evolution API

Interact with Evolution API

Overview

This node, named "Evolution API," allows users to interact with the Evolution API by performing various operations on different resources. Specifically, for the resource "Perfil" and operation "Buscar Configurações De Privacidade" (Search Privacy Settings), it retrieves privacy configuration data related to a user profile or instance.

Common scenarios where this node is beneficial include:

  • Fetching privacy settings of a user profile in an automated workflow.
  • Integrating privacy configuration retrieval into larger automation processes.
  • Monitoring or auditing privacy configurations programmatically.

For example, a user might automate the process of checking privacy settings for multiple instances by looping over instance names and using this node to fetch their respective privacy configurations.

Properties

Name Meaning
Nome Da Instância The name of the instance to query. This string input is required and specifies which instance's privacy settings to retrieve.

Output

The node outputs a JSON array containing the privacy configuration data retrieved from the Evolution API for the specified instance. Each item in the output array represents the privacy settings associated with the given instance name.

If the API returns binary data (not indicated in the provided code), it would be included accordingly, but based on the static analysis, the output is JSON-formatted data representing privacy configurations.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node expects the Evolution API to be accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Operation Not Supported Error: If the node throws an error stating the operation is not supported, verify that the resource is set to "Perfil" and the operation to "Buscar Configurações De Privacidade". Also, ensure the node version supports this operation.
  • Missing or Invalid Instance Name: Since "Nome Da Instância" is required, leaving it empty or invalid may cause the API call to fail or return no data.
  • Authentication Issues: Ensure the API key credential is correctly configured and has sufficient permissions to access privacy settings.
  • API Connectivity Problems: Network issues or incorrect API endpoint configurations can lead to failures; verify connectivity and endpoint correctness.

Links and References

Discussion