Actions64
- Instance Actions
- Chat Actions
- Message Actions
- Group Actions
- Profile Actions
- Event Actions
- Integration Actions
Overview
The node named "Evolution API" provides an interface to interact with the Evolution API service. Specifically, for the Chat resource and the Check Number operation, 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 item in the array corresponds to one of the input numbers and includes details about its validation status or other relevant metadata returned by the Evolution API.
If the API supports binary data output (e.g., media files), it would be included accordingly, but based on the provided code and properties, the primary output is structured JSON data representing the check results.
Dependencies
- Requires an API key credential for the Evolution API to authenticate requests.
- The base URL for API requests is
https://doc.evolution-api.com/api-reference. - The node expects JSON responses and sends requests with appropriate headers (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Unsupported operation error: If the node throws an error stating the operation is unsupported, ensure that the Resource is set to "Chat" and Operation to "Check Number". Other combinations may not be implemented.
- Invalid or missing API credentials: The node requires a valid API key credential. Verify that the credential is correctly configured in n8n.
- Malformed numbers input: The "Numbers" property must be a comma-separated string of phone numbers. Incorrect formatting may cause API errors or unexpected results.
- API connectivity issues: Network problems or incorrect base URL configuration can lead to request failures. Confirm internet access and correct API endpoint usage.
Links and References
- Evolution API Documentation – Official API reference for detailed information on endpoints and parameters.