Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Buscar Foto De Perfil" (Fetch Profile Picture), it retrieves the profile picture of a specified contact within a given instance. This functionality is useful in scenarios where you want to programmatically obtain user profile images from a chat system, such as displaying contact avatars in a custom dashboard or automating contact management workflows.
Practical examples include:
- Automatically fetching and displaying profile pictures of contacts in a CRM system.
- Archiving profile pictures of chat contacts for record-keeping.
- Enhancing chatbot interfaces by showing user avatars dynamically.
Properties
Name | Meaning |
---|---|
Nombre De La Instancia | The name of the chat instance to connect to. This identifies which chat environment to use. |
Contacto | The phone number of the contact whose profile picture is to be fetched (e.g., +1234567890). |
Output
The node outputs a JSON array containing the result of the profile picture fetch operation. Each item in the array corresponds to one execution result and includes data about the contact's profile picture. The exact structure depends on the Evolution API response but typically includes fields such as the URL or binary data reference of the profile picture.
If the node supports binary data output (not explicitly shown in the provided code), it would represent the profile picture image itself, allowing further processing or saving within n8n workflows.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference
. - Proper configuration of the "Nombre De La Instancia" and "Contacto" properties is necessary for successful operation.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the Resource is set to "Chat" and the Operation to "Buscar Foto De Perfil". Also, ensure the node version and API support this operation.
- Invalid or missing credentials: Ensure that the API authentication token or key is correctly configured in the node credentials.
- Incorrect instance name or contact number: Double-check the "Nombre De La Instancia" and "Contacto" inputs for correctness and proper formatting (e.g., international phone number format).
- Network or API errors: Check network connectivity and API service status if requests fail or time out.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes