Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

This node, named "Evolution API Direct," allows users to interact with the Evolution API by specifying a direct server URL and an API key. It supports various resources and operations; in this case, focusing on the Chat resource with the Buscar Foto Do Perfil (Fetch Profile Picture) operation. The node is useful for retrieving the profile picture of a specific contact from the Evolution API chat system.

Typical use cases include:

  • Automating retrieval of user profile pictures for display or processing.
  • Integrating Evolution API chat data into workflows that require user images.
  • Synchronizing contact profile pictures between systems.

Properties

Name Meaning
Server URL The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API instance.
Nome Da Instância The name of the Evolution API instance you want to connect to.
Contato The phone number of the contact whose profile picture you want to fetch (e.g., 5511999999999).

Output

The node outputs a JSON array where each item corresponds to the result of the requested operation. For the "Buscar Foto Do Perfil" operation, the output JSON contains the profile picture data associated with the specified contact number.

If the profile picture is returned as binary data, it would typically be included in the binary property of the output item, representing the image file. However, based on the provided code snippet, the exact structure of the output JSON or binary data is not explicitly detailed.

Dependencies

  • Requires access to the Evolution API server via the provided Server URL.
  • Needs a valid API key credential for authentication.
  • The node depends on the Evolution API's chat service being available and accessible.
  • No additional external libraries beyond n8n core dependencies are indicated.

Troubleshooting

  • Operation Not Supported Error: If you select an unsupported operation or resource, the node throws an error stating the operation is not supported. Ensure you choose valid combinations of resource and operation.
  • Authentication Failures: Incorrect or missing API key or server URL will cause authentication errors. Verify credentials and endpoint correctness.
  • Invalid Contact Number: Providing an incorrectly formatted contact number may lead to no results or errors. Use the international format without symbols (e.g., 5511999999999).
  • Network Issues: Connectivity problems to the Evolution API server will prevent successful execution.
  • Empty or Missing Profile Picture: If the contact has no profile picture, the output might be empty or null. Handle such cases gracefully in downstream workflow steps.

Links and References

Discussion