Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to perform various operations related to WhatsApp messaging and instance management. Specifically, for the Chat resource and the Verificar Número (Check Number) operation, it verifies whether a given phone number is registered on WhatsApp.

Common scenarios where this node is beneficial include:

  • Validating if a contact's phone number is active on WhatsApp before attempting to send messages.
  • Filtering contacts in bulk to ensure messages are only sent to valid WhatsApp users.
  • Automating workflows that depend on WhatsApp presence verification.

Practical example:

  • Before sending a promotional message campaign, use this node to check each recipient’s number to avoid sending messages to non-WhatsApp numbers, improving delivery rates and reducing errors.

Properties

Name Meaning
Instance Name The name of the Evolution API instance to use. This identifies which WhatsApp instance the operation will be performed on.

Output

The output JSON contains the response from the Evolution API indicating whether the specified number is a WhatsApp user. It typically includes:

  • A success flag indicating if the operation was successful.
  • Data about the number's WhatsApp status (e.g., true/false or detailed info).
  • A timestamp marking when the operation was completed.

If the API returns no data, the output defaults to a success message with a timestamp.

No binary data output is produced by this operation.

Dependencies

  • Requires an authenticated connection to the Evolution API v2 via an API key credential configured in n8n.
  • The node depends on the Evolution API service being accessible and the specified instance name existing and connected.

Troubleshooting

  • Common issues:

    • Invalid or missing instance name: Ensure the "Instance Name" property matches an active instance configured in your Evolution API account.
    • Network or authentication errors: Verify API credentials and network connectivity.
    • Number format errors: Confirm the phone number is in the correct international format expected by the API.

  • Error messages:

    • Authentication failures: Check that the API key credential is correctly set up and has necessary permissions.
    • Instance not found or disconnected: Make sure the instance name exists and is currently connected.
    • Invalid number format: Validate the input number format before running the node.

Resolving these usually involves verifying configuration settings, credentials, and input data formats.

Links and References

Discussion