Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
This node, named "Evolution API," allows users to interact with the Evolution API service. Specifically, for the resource Chat and operation Verificar Número (Check Number), it verifies a list of phone numbers against the Evolution API. This is useful in scenarios where you need to validate multiple phone numbers at once, for example, to check if they are registered or active on a messaging platform before sending messages.
Practical examples include:
- Bulk validating customer phone numbers before launching a marketing campaign.
- Checking user phone numbers during onboarding to ensure they are reachable via chat.
- Filtering out invalid or inactive numbers from contact lists.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance to use for the API interaction. |
| Números | A comma-separated list of phone numbers to verify. |
Output
The node outputs a JSON array where each element corresponds to the verification result of one phone number from the input list. Each item typically contains details about the number's status as returned by the Evolution API, such as whether the number is valid, registered, or any other metadata provided by the API.
If the API supports binary data output (e.g., images or files), this node would summarize that binary data represents related content, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the Evolution API base URL
https://doc.evolution-api.com/api-reference. - Proper configuration of the API key credential within n8n is necessary.
- Network access to the Evolution API endpoint must be available.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you select the correct resource ("chat-api") and operation ("check-number").
- Invalid or missing credentials: The node requires a valid API key credential. Errors related to authentication usually mean the credential is missing, expired, or incorrect.
- Malformed phone numbers: Inputting phone numbers in an incorrect format or without proper separation (commas) may cause the API to reject them or return errors.
- API rate limits or downtime: If the Evolution API service is down or rate-limited, requests will fail. Check API status and retry later.
Links and References
- Evolution API Documentation (official API reference)
- n8n documentation on creating custom nodes