Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a server URL and an API key. It supports various resources and operations, including the "Perfil" resource with the "Buscar Perfil" operation. This operation fetches profile information for a specified contact number from the Evolution API instance.
This node is beneficial when you need to integrate Evolution API data retrieval into your workflows, such as fetching user profiles or business profiles dynamically based on contact numbers. For example, it can be used in customer support automation to retrieve detailed profile information before responding to inquiries.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server (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 contact number whose profile you want to fetch. |
Output
The node outputs a JSON array where each element contains the profile data retrieved from the Evolution API for the specified contact. The structure of the JSON depends on the API response but typically includes fields related to the profile details of the contact.
If the API returns binary data (not indicated here), it would be included accordingly, but this node primarily deals with JSON profile information.
Dependencies
- Requires access to the Evolution API endpoint specified by the Server URL.
- Requires a valid API key for authentication.
- Needs the instance name of the Evolution API to target the correct environment.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Operation not supported error: If you select an unsupported operation-resource combination, the node throws an error indicating the operation is not supported. Ensure you use valid combinations.
- Authentication errors: Invalid or missing API keys will cause authentication failures. Verify that the API key is correct and has necessary permissions.
- Invalid Server URL: Providing an incorrect or unreachable server URL will result in connection errors. Confirm the URL is accessible and correctly formatted.
- Missing required properties: All required properties must be provided; otherwise, the node will fail to execute properly.
Links and References
- Evolution API Documentation (as referenced in the code's baseURL)
- General n8n documentation on HTTP Request nodes for understanding API integrations