Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource Chat and operation Buscar Foto Do Perfil (Fetch Profile Picture), it enables fetching 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 (e.g., 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 related to the profile picture URL or binary data representing the image. If the node supports binary output, it would represent the profile picture file itself; otherwise, the JSON will contain 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 environment variables are explicitly required beyond the API authentication setup.

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 choose valid combinations of resource and operation.
  • Invalid or missing credentials: Authentication failures may occur if the API key or token is incorrect or missing. Verify that the API credentials are correctly set up in n8n.
  • Incorrect phone number format: The contact number must be in the correct international format (e.g., 5511999999999). Invalid formats may cause the API call to fail.
  • Instance name errors: Providing an incorrect or non-existent instance name may lead to failed requests. Confirm the instance name matches what is configured in the Evolution API.

Links and References

Discussion