Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" provides integration with the Evolution API service, allowing users to perform various operations on different resources. Specifically, for the resource Chat and operation Buscar Foto Do Perfil (Fetch Profile Picture), the node fetches the profile picture of a specified contact number from a given instance. This is useful in scenarios where you want to retrieve and display or process the profile image associated with a chat contact, such as in customer support dashboards, contact management systems, or messaging automation workflows.

Properties

Name Meaning
Nome Da Instância The name of the instance to connect to. This identifies which Evolution API instance to use.
Contato The phone number of the contact whose profile picture you want to fetch. Format example: 5511999999999

Output

The node outputs a JSON array containing the result of the profile picture fetch operation. The exact structure depends on the Evolution API response but typically includes data about the profile picture URL or binary data representing the image. If the node supports binary output, it would represent the profile picture file content; otherwise, it will provide metadata or a link to the image.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node expects the Evolution API base URL and headers to be configured internally.
  • No additional external dependencies are indicated beyond the Evolution API service.

Troubleshooting

  • Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the function is not supported. Ensure you select the correct resource ("chat") and operation ("fetch-profile-picture").
  • Invalid or missing instance name: The instance name is required; leaving it empty will likely cause the request to fail.
  • Incorrect contact number format: The contact number must be in the correct international format (e.g., 5511999999999). Invalid formats may lead to errors or no data returned.
  • API authentication issues: Make sure the API key credential is correctly set up and has the necessary permissions.
  • Network or API errors: Check network connectivity and Evolution API service status if requests fail unexpectedly.

Links and References

Discussion