NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Overview

The NotificaMe Hub node for n8n enables integration with the NotificaMe Hub API, specifically allowing you to send text messages via the WebChat channel. The "Enviar Texto" operation under the "WebChat" resource is designed to deliver a custom message to a specified recipient within a particular WebChat channel.

Common scenarios:

  • Sending automated notifications or alerts to users in a WebChat environment.
  • Building chatbots or customer support flows that require sending messages to users.
  • Integrating external systems (e.g., CRMs, helpdesks) to trigger real-time communication with customers via WebChat.

Practical example:
When a new support ticket is created in your system, use this node to automatically notify the user through WebChat with the ticket details and next steps.


Properties

Below are the input properties required for the "WebChat" → "Enviar Texto" operation:

Display Name Type Description
ID Do Canal String ID do canal do WebChat (WebChat channel ID). This identifies which WebChat channel will be used to send the message.
ID Do Destinatário String ID do destinatário no WebChat (Recipient ID). Specifies the user who will receive the message.
Mensagem String Texto da mensagem a ser enviada (Message text). The actual content of the message to be sent.

All fields are required.


Output

The node outputs a json object containing the response from the NotificaMe Hub API after attempting to send the message. While the exact structure depends on the API's response, it typically includes:

  • status: Indicates success or failure of the message delivery.
  • messageId: Unique identifier for the sent message.
  • timestamp: When the message was processed.
  • error (optional): If an error occurred, details about the issue.

Note: The output does not include binary data.


Dependencies

  • External Service: Requires access to the NotificaMe Hub API.
  • API Credentials: You must configure the notificamehubApi credential in n8n.
  • n8n Configuration: No additional configuration is needed beyond setting up the credentials.

Troubleshooting

Common issues:

  • Invalid Channel or Recipient ID: If the provided IDs do not exist or are incorrect, the API may return an error indicating the resource was not found.
  • Missing Required Fields: All three properties are mandatory. Omitting any will result in validation errors.
  • Authentication Errors: If the API key is missing or invalid, you'll receive authentication/authorization errors.

Common error messages and resolutions:

  • "Channel not found": Verify the "ID Do Canal" value.
  • "Recipient not found": Check the "ID Do Destinatário".
  • "Unauthorized": Ensure your API credentials are correctly set up in n8n.
  • "Message text required": Make sure the "Mensagem" field is filled.

Links and References


Discussion