Evolution API

Overview

The "Verificar Número" operation of the "Chat" resource in this custom n8n node allows users to check (verify) a list of phone numbers using the Evolution API. This is useful for scenarios where you need to validate whether certain phone numbers are active, registered, or available for messaging before attempting further communication. For example, businesses can use this feature to clean up contact lists, ensure message deliverability, or automate onboarding processes by verifying user-provided numbers.

Properties

Output

• The output will be a JSON array, where each item corresponds to the verification result for a number provided.
• Each object in the array contains the verification details for a specific number. The exact fields depend on the Evolution API's response, but typically include:
  • The original number checked
  • Status/result of the verification (e.g., valid/invalid, exists/does not exist)
  • Any additional metadata returned by the API

Example Output:

[
  {
    "number": "+5511999999999",
    "status": "valid",
    "details": { /* ...additional info... */ }
  },
  {
    "number": "+5511888888888",
    "status": "invalid"
  }
]

Dependencies

• External Service: Requires access to the Evolution API.
• API Key/Credentials: You must configure the evolutionApi credentials in n8n.
• n8n Configuration: Ensure that the node is properly set up with the required credentials and that your instance has internet access to reach the Evolution API endpoint.

Troubleshooting

• Missing Credentials: If the evolutionApi credentials are not configured, the node will fail to execute. Make sure to add and select the correct credentials in n8n.
• Unsupported Operation Error: If you see an error like "Operação não suportada" ("Operation not supported"), it means the selected operation is not implemented for the chosen resource. Double-check your resource and operation selection.
• Invalid Numbers Format: Ensure that the "Números" property is a comma-separated string of valid phone numbers. Incorrect formatting may lead to API errors or failed verifications.
• API Errors: If the Evolution API returns an error (e.g., due to rate limits, invalid instance name, or network issues), the node will throw an error with the API's message. Review the error details and consult the API documentation for resolution.

Links and References

• Evolution API Documentation
• n8n Credentials Documentation
• n8n Custom Nodes Guide