Evolution API

Interagir com a Evolution API v2
Join our community

Actions53

Overview

This node integrates with the Evolution API v2 to send various types of WhatsApp messages and manage instances, groups, chats, events, and integrations. Specifically, for the Mensagem (Message) resource with the Enviar Enquete (Send Poll) operation, it allows sending a poll message to a specified recipient number through a selected instance.

Use cases include automating customer surveys, collecting feedback, or running quick polls via WhatsApp in workflows. For example, a business can send a poll to customers asking about their satisfaction after a service interaction.

Properties

Name Meaning
Instance Name The name of the WhatsApp instance used to send the poll message.
Number The recipient's phone number to which the poll will be sent.

Note: The provided properties JSON only includes "Instance Name" and "Number" as inputs relevant to this resource-operation combination.

Output

The node outputs a JSON array where each item corresponds to the result of sending the poll message for each input item processed. The output structure includes:

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

If the API returns an array of results, each is parsed and included in the output items. If the API returns a string, the node attempts to parse it as JSON; otherwise, it wraps it in a value field.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API v2.
  • The node uses HTTP requests to the Evolution API endpoints.
  • Proper configuration of the API credential in n8n is necessary.
  • The "Instance Name" must correspond to a valid and connected WhatsApp instance managed by the Evolution API.

Troubleshooting

  • Common issues:

    • Invalid or disconnected instance name: Ensure the instance exists and is connected.
    • Incorrect recipient number format: Use international format without special characters.
    • API authentication errors: Verify that the API key credential is correctly configured and has permissions.
    • Network or API downtime: Check connectivity and Evolution API status.

  • Error messages:

    • Errors thrown by the API are caught and returned as error messages in the output if "Continue On Fail" is enabled.
    • Parsing errors may occur if the API returns unexpected response formats; ensure the API version matches the node expectations.

Links and References

Discussion