Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
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 retrieving the profile picture of a specified contact within a given instance. This is useful in scenarios where you want to programmatically access user profile images from a chat system, for example, to display them in dashboards, automate contact management, or enrich communication logs.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the chat instance 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 containing the result of the profile picture fetch operation. The exact structure depends on the Evolution API response but typically includes data such as the URL or binary data reference of the profile picture. If the node supports binary data output, it would represent the profile picture image itself; otherwise, it provides 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 service to be accessible and properly configured.
- 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 that the Resource is set to "Chat" and Operation to "Buscar Foto Do Perfil".
- Missing Required Parameters: Both "Nome Da Instância" and "Contato" are required. Omitting these will cause errors or failed requests.
- API Authentication Issues: Invalid or missing API credentials will prevent successful calls. Verify that the API key credential is correctly configured.
- Invalid Contact Number Format: The contact number must follow the expected format (e.g., country code + number without spaces). Incorrect formatting may lead to failed lookups.
Links and References
- Evolution API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes