NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Actions31

Overview

This node integrates with the NotificaMe Hub API to send interactive WhatsApp messages featuring a Call To Action (CTA) button. It allows users to send a message with a header, body text, footer, and a clickable button that directs the recipient to a specified URL.

Common scenarios for this node include:

  • Sending promotional messages with a direct link to a product or service.
  • Sharing event invitations where recipients can click a button to RSVP or get more information.
  • Providing quick access to customer support or feedback forms via a button in WhatsApp messages.

Practical example: A business wants to notify customers about a new product launch and includes a "Buy Now" button linking directly to the product page.

Properties

Name Meaning
Token Do Canal The WhatsApp channel token used for authenticating the API request.
Número Do Destinatário Recipient's phone number in international format (e.g., 5511999999999).
Texto Do Cabeçalho Text displayed as the header of the WhatsApp message.
Texto Da Mensagem Main body text of the WhatsApp message.
Texto Do Rodapé Optional text shown at the footer of the message.
Texto Do Botão Text displayed on the CTA button (default is "Clique aqui").
URL Do Botão URL where the button will redirect the user upon clicking.

Output

The node outputs JSON data representing the response from the NotificaMe Hub API after sending the WhatsApp interactive message. This typically includes confirmation details such as message ID, status, timestamps, or error information if the message failed to send.

If the node supports binary data output (not indicated here), it would represent media content or attachments sent or received, but for this operation, the output is purely JSON-based.

Dependencies

  • Requires an active WhatsApp channel token for authentication with the NotificaMe Hub API.
  • The node depends on the NotificaMe Hub API endpoint https://hub.notificame.com.br/v1.
  • Proper configuration of the API key credential within n8n is necessary.
  • Internet connectivity to reach the external NotificaMe Hub service.

Troubleshooting

  • Invalid Token or Authentication Failure: If the provided channel token is incorrect or expired, the API will reject the request. Ensure the token is valid and has the required permissions.
  • Incorrect Recipient Number Format: The recipient number must be in international format without spaces or special characters. Errors may occur if the format is invalid.
  • URL Validation: The button URL must be a valid and reachable URL. Invalid URLs might cause the message to fail.
  • API Rate Limits or Quotas: Exceeding allowed API usage limits could result in errors or throttling.
  • Missing Required Fields: Omitting mandatory fields like header text, body text, button text, or URL will cause validation errors.
  • Network Issues: Connectivity problems between n8n and the NotificaMe Hub API can cause timeouts or failures.

To resolve these issues:

  • Double-check all input values for correctness.
  • Verify API credentials and permissions.
  • Test the URL separately to ensure it is accessible.
  • Monitor API usage and respect rate limits.
  • Check network connectivity and firewall settings.

Links and References

Discussion