Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node allows sending interactive button messages via a messaging API. It is designed to send messages that include a title, description, optional footer, and up to three interactive buttons of various types (reply, copy, URL, or call). This functionality is useful for creating engaging chat experiences where users can quickly respond, copy text, open links, or initiate calls directly from the message.

Common scenarios include:

  • Customer support bots providing quick reply options.
  • Marketing campaigns with call-to-action buttons linking to URLs.
  • Service notifications allowing users to copy codes or contact support by phone.

Example: Sending a message titled "Order Update" with buttons like "Track Order" (URL), "Call Support" (call), and "Copy Promo Code" (copy).

Properties

Name Meaning
Instance Name The name of the instance that will send the buttons.
Recipient Number The recipient's phone number or identifier to whom the message will be sent.
Title The main title text of the message containing buttons.
Description A descriptive text providing details about the message content.
Footer Optional footer text displayed at the bottom of the message.
Buttons Up to 3 buttons to include in the message. Each button has:
- Type The type of button: reply, copy, url, or call.
- Button Text The visible text on the button.
- ID (For reply type) Identifier returned when the button is clicked.
- Copy Code (For copy type) Text/code that will be copied to clipboard when the button is clicked.
- URL (For url type) Web address opened when the button is clicked.
- Phone Number (For call type) Phone number dialed when the button is clicked.

Output

The node outputs a JSON array where each item corresponds to the result of sending the button message. The exact structure depends on the underlying API response but generally includes confirmation of message delivery status and any relevant metadata.

If the node supports binary data output (not indicated here), it would typically represent media attachments or message payloads; however, this node focuses on JSON message sending.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API service.
  • The node configuration must include valid credentials and correct instance naming.
  • Network access to the Evolution API endpoint (https://doc.evolution-api.com/api-reference) is necessary.

Troubleshooting

  • Unsupported operation error: Occurs if the specified resource or operation is not implemented. Verify that "messages-api" resource and "send-buttons" operation are correctly selected.
  • Missing required fields: Ensure all mandatory properties such as Instance Name, Recipient Number, Title, Description, and button-specific fields are provided.
  • API authentication failures: Check that the API key credential is valid and properly configured.
  • Button limit exceeded: Only up to 3 buttons are allowed; adding more will cause errors.
  • Invalid button type or missing button parameters: Each button type requires specific fields (e.g., URL for url type); ensure these are correctly set.

Links and References

Discussion