Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Check Number," it allows users to verify a list of phone numbers. This can be useful in scenarios where you need to validate multiple contact numbers before sending messages or performing further actions, ensuring that only valid numbers are processed.
For example, a marketing automation workflow could use this node to filter out invalid phone numbers from a customer list before launching a campaign, reducing errors and improving delivery rates.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the Evolution API instance to connect to. |
| Numbers | A comma-separated list of phone numbers to check for validity or status via the API. |
Output
The node outputs a JSON array containing the results of the number checks. Each element in the array corresponds to one of the input numbers and includes details returned by the Evolution API about that number's status or validity.
If the API supports binary data (e.g., media or attachments), the node would handle it accordingly, but based on the provided code and properties, the output is primarily JSON data related to number verification.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for API requests is set to
https://doc.evolution-api.com/api-reference. - The node depends on the Evolution API service being available and reachable.
- Proper configuration of the "Instance Name" property is necessary to target the correct API instance.
Troubleshooting
- Operation not supported error: If you select an operation or resource combination that is not implemented, the node will throw an error stating the function is not supported. Ensure you use valid resource-operation pairs.
- Invalid or missing API credentials: The node requires valid authentication credentials. Failure to provide these will result in authorization errors.
- Malformed numbers input: The "Numbers" property expects a comma-separated string of phone numbers. Incorrect formatting may cause the API call to fail or return unexpected results.
- Network issues: Connectivity problems to the Evolution API endpoint will cause request failures. Verify network access and API availability.
Links and References
- Evolution API Documentation (base URL used by the node)
- n8n documentation on Creating Custom Nodes