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 with the Evolution API by specifying a direct server URL and an API key. It supports various resources and operations, including the "Chat" resource with the "Verificar Número" (Check Number) operation. This particular operation enables users to verify one or multiple phone numbers against the Evolution API service.
Common scenarios for this node include:
- Validating phone numbers before sending messages or notifications.
- Checking the status or existence of numbers in the Evolution API system.
- Integrating number verification into automated workflows for customer communication.
For example, a user can input a list of phone numbers separated by commas, and the node will return verification results indicating which numbers are valid or active according to the Evolution API.
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. |
| Números | A comma-separated list of phone numbers to verify using the Evolution API. |
Output
The node outputs a JSON array where each element corresponds to the result of verifying the provided phone numbers. Each JSON object typically contains information about the verification status of a number, such as whether it is valid, active, or any related metadata returned by the Evolution API.
If the API returns binary data (not indicated here), it would be summarized accordingly, but based on the code and properties, the output is primarily JSON structured data.
Dependencies
- Requires access to the Evolution API via a reachable server URL.
- Needs a valid API key credential for authentication.
- The node expects the user to provide the instance name of the Evolution API.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Common Issues:
- Incorrect or missing Server URL or API Key will cause authentication failures.
- Providing improperly formatted phone numbers (e.g., missing commas or invalid characters) may lead to errors or unexpected results.
- Using an unsupported operation or resource will throw an error indicating the operation is not supported.
Error Messages:
"Operação não suportada."— This means the selected operation for the resource is not implemented. Verify that the resource and operation names are correct.- Authentication errors due to invalid API keys or incorrect URLs will typically come from the API response; ensure credentials and URLs are accurate.
Resolution Tips:
- Double-check the API key and server URL.
- Ensure the instance name matches exactly what is configured in the Evolution API.
- Format the list of numbers correctly, separating them with commas without extra spaces or invalid characters.
Links and References
- Evolution API Documentation (as referenced in the default base URL)
- Consult your Evolution API provider for details on API key management and instance configuration.