Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Resource "Profile" and Operation "Buscar Perfil Profissional" (Fetch Professional Profile), it fetches professional profile information of a contact based on the provided contact number. This node is useful in scenarios where you need to retrieve detailed professional profile data from an external system, such as integrating contact management or CRM systems with Evolution API to enrich contact details.
Practical examples include:
- Automatically fetching and updating professional profiles of contacts when new data arrives.
- Enriching customer records with professional information for marketing or support purposes.
- Integrating with communication platforms to display professional profile info during interactions.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Contact | The contact number (remoteJid) for which the professional profile will be fetched. |
Output
The output of the node is a JSON array containing the fetched professional profile data corresponding to the specified contact. Each item in the array represents the profile information retrieved from the Evolution API.
If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.
Dependencies
- Requires an API key credential for authenticating with the Evolution API service.
- The node expects the Evolution API base URL
https://doc.evolution-api.com/api-referenceto be accessible. - Proper configuration of the "Instance Name" property to specify which Evolution API instance to use.
Troubleshooting
- Operation not supported error: If the operation "Buscar Perfil Profissional" is not implemented or misspelled, the node throws an error indicating the function is not supported. Ensure the operation name matches exactly.
- Missing required parameters: Both "Instance Name" and "Contact" are required. Omitting these will cause errors.
- API authentication failures: If the API key or credentials are invalid or missing, requests to the Evolution API will fail.
- Network issues: Connectivity problems to the Evolution API endpoint will prevent successful data retrieval.
Links and References
- Evolution API Documentation (base URL referenced in the node)
- n8n documentation on Creating Custom Nodes