Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to perform various messaging and instance management operations. Specifically, for the Mensagem (Message) resource and the Enviar Contato (Send Contact) operation, it allows sending a contact card to a specified recipient number via a configured Evolution API instance.

Common scenarios where this node is beneficial include automating customer support or sales workflows by programmatically sharing contact information through WhatsApp or similar messaging platforms managed by the Evolution API. For example, a business can automatically send a contact card of a sales representative to a lead after a form submission.

Properties

Name Meaning
Instance Name The name of the Evolution API instance to use for sending the contact.
Number The recipient's phone number to which the contact will be sent.

Note: Although your provided properties JSON only includes "Instance Name" and "Number", the node supports many other message-related operations with additional properties (not detailed here as per your request).

Output

The node outputs a JSON array where each item corresponds to the result of an individual execution for each input item. The output structure includes:

  • success: A boolean indicating if the operation was successful.
  • message (optional): A success message string.
  • timestamp: ISO string timestamp of when the operation completed.
  • Other fields returned by the Evolution API response, parsed from JSON if possible.

If the API returns multiple items, they are included in an items array with a count of total items.

The node does not explicitly output binary data for this operation.

Dependencies

  • Requires an authenticated connection to the Evolution API v2 via an API key credential configured in n8n.
  • The node uses HTTP requests to the Evolution API endpoints, so network connectivity to the API server is necessary.
  • Proper configuration of the Evolution API instance name is required to route requests correctly.

Troubleshooting

  • Common Issues:

    • Incorrect or missing instance name may cause the API call to fail.
    • Invalid or improperly formatted recipient phone numbers can result in errors.
    • Network issues or invalid API credentials will prevent successful communication with the Evolution API.

  • Error Messages:

    • Errors thrown by the node typically contain the API error message. If the node is set to continue on failure, errors are returned as part of the output JSON with an error field.
    • Common resolution steps include verifying the instance name, checking the phone number format, and ensuring valid API authentication.

Links and References

Discussion