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 operation "Buscar Perfil Profissional" (Fetch Professional Profile). This node is useful for retrieving professional profile information of contacts from the Evolution API system.
Typical use cases include:
- Fetching detailed professional profiles of contacts by their contact number.
- Integrating Evolution API data into workflows for CRM, customer support, or analytics.
- Automating retrieval of profile data for further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server endpoint (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 specific Evolution API instance you want to target. |
| Contato | The contact number (remoteJid) whose professional profile you want to fetch. |
Output
The node outputs a JSON array where each element corresponds to the fetched professional profile data for the specified contact. The structure of the JSON output depends on the Evolution API response but generally includes fields related to the professional profile details of the contact.
If the API returns binary data (not indicated in the provided code), it would be included accordingly, but based on the static analysis, the output is JSON only.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires a valid API key credential for authentication.
- The node expects the user to provide the correct server URL and instance name.
- No additional external dependencies are indicated beyond standard HTTP request capabilities.
Troubleshooting
- Operation not supported error: If the node throws an error stating the operation is not supported, verify that the resource and operation names are correctly set to "Perfil" and "Buscar Perfil Profissional" respectively.
- Authentication errors: Ensure the API key is valid and has sufficient permissions for the requested operation.
- Invalid server URL: Confirm the server URL is complete and reachable.
- Missing required parameters: Make sure all required properties (Server URL, API Key, Instance Name, Contact) are provided.
- Empty or unexpected response: Check if the contact number exists in the Evolution API system and that the instance name is correct.
Links and References
- Evolution API official documentation (replace with actual URL): https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/