Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

This node allows sending interactive button messages through the Evolution API. It is designed to send a message with up to three customizable buttons to a specified recipient number via an instance of the Evolution messaging service.

Common scenarios include:

  • Sending quick reply options to users in chatbots or customer support.
  • Providing clickable URLs, phone call links, or copy-to-clipboard buttons within messages.
  • Enhancing user engagement by offering multiple interaction choices directly in the message.

For example, a business could send a message with buttons like "Confirm Order" (reply), "Visit Website" (URL), and "Call Support" (call) to streamline customer interactions.

Properties

Name Meaning
Server URL The full URL of your Evolution API endpoint.
API Key The API key for authenticating requests to your Evolution API instance or global account.
Nome Da Instância The name of the Evolution API instance that will send the buttons.
Número Do Destinatário The recipient's phone number to which the button message will be sent.
Título The title text of the button message.
Descrição The description text of the button message.
Rodapé Optional footer text displayed at the bottom of the message.
Botões Up to 3 buttons to include in the message. Each button can be one of the following types:
- Resposta (reply): A button that sends a predefined reply ID when clicked.
- Copiar (copy): A button that copies a code/text to clipboard.
- URL: A button that opens a specified URL.
- Ligar (call): A button that initiates a phone call to a given number.

Each button requires specific fields depending on its type:

  • Reply: Texto Do Botão (button label), ID (reply identifier)
  • Copy: Texto Do Botão, Código Para Copiar (text to copy)
  • URL: Texto Do Botão, URL
  • Call: Texto Do Botão, Número De Telefone

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the button message. The exact structure depends on the API response but typically includes status information about the message delivery.

No binary data output is indicated.

Dependencies

  • Requires access to the Evolution API endpoint specified by the Server URL.
  • Requires a valid API key credential for authentication.
  • Proper configuration of the instance name and recipient number is necessary.
  • Network connectivity to the Evolution API service.

Troubleshooting

  • Operation not supported error: If the selected operation or resource is not implemented, the node throws an error indicating unsupported operation. Ensure you select "Enviar Botões" under the "Mensagem" resource.
  • Authentication failures: Invalid or missing API key will cause authorization errors. Verify the API key is correct and has necessary permissions.
  • Invalid recipient number: Ensure the recipient phone number is correctly formatted and active.
  • Button configuration errors: Each button must have required fields filled according to its type; missing fields will likely cause request failures.
  • API endpoint issues: Confirm the Server URL is reachable and correct.

Links and References

Discussion