Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" allows users to interact with the Evolution API service. Specifically, for the Chat resource and the List Contacts operation, it retrieves a list of contacts from the specified instance of the Evolution API chat system. This is useful in scenarios where you want to automate fetching contact lists for messaging, customer support, or CRM integrations.
For example, you might use this node to:
- Retrieve all contacts from a chat instance to sync with another system.
- Fetch a specific contact's details by providing their unique identifier.
- Automate workflows that require up-to-date contact information from the Evolution API chat service.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API chat instance you want to connect to. |
| List All | Boolean option to either list all contacts (true) or specify a single contact (false). |
| Contact | When List All is false, specify the unique identifier (contact number) of the contact to retrieve. |
Output
The node outputs an array of JSON objects representing contacts retrieved from the Evolution API chat instance. Each object corresponds to a contact's data as returned by the API. The exact structure depends on the API response but typically includes identifiers, names, and possibly status or metadata about each contact.
If binary data were involved (e.g., profile pictures), it would be included in the output's binary field, but based on the provided code and properties, this node focuses on JSON contact data only.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n to authorize requests.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - No additional external dependencies are indicated beyond the Evolution API and its credentials.
Troubleshooting
- Unsupported operation error: If you select a resource-operation combination not implemented, the node will throw an error stating the function is unsupported. Ensure you choose valid resource and operation pairs.
- Missing or invalid credentials: The node requires proper API authentication; missing or incorrect credentials will cause request failures.
- Invalid instance name or contact ID: Providing an incorrect instance name or contact identifier may result in empty results or errors from the API.
- Network issues: Connectivity problems to the Evolution API endpoint will prevent successful execution.
To resolve these issues:
- Verify your API credentials and permissions.
- Double-check the instance name and contact IDs.
- Confirm network connectivity and API availability.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on creating custom nodes for further customization guidance