NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Actions31

Overview

The "Definir Webhook" operation under the "Revenda" resource in this node allows users to configure webhook URLs for a specific channel token. This setup enables the NotificaMe Hub API to send event notifications to the specified URLs whenever relevant events occur on that channel.

This operation is beneficial when you want to automate workflows triggered by real-time events from a communication channel managed via NotificaMe Hub. For example, you can set up a webhook URL to receive incoming message notifications or status updates, enabling your system to react immediately (e.g., logging messages, triggering alerts, or updating CRM records).

Practical examples:

  • Setting a primary webhook URL to receive all event callbacks for a sales channel.
  • Adding a secondary webhook URL to forward events to an additional monitoring service or backup endpoint.

Properties

Name Meaning
Token Do Canal The channel token for which you want to receive events. This is a required secret string.
URL Do Webhook The primary URL where event notifications will be sent. Required string.
URL Do Webhook Secundário An optional secondary URL to also receive event notifications.

Output

The node outputs JSON data representing the response from the NotificaMe Hub API after setting the webhook(s). This typically includes confirmation of the webhook registration and any related metadata returned by the API.

There is no indication that this operation outputs binary data.

Dependencies

  • Requires an API key credential for authenticating with the NotificaMe Hub API.
  • The base URL for API requests is https://hub.notificame.com.br/v1.
  • Proper network connectivity to the NotificaMe Hub service and the webhook URLs must be ensured.

Troubleshooting

  • Invalid Channel Token: If the provided channel token is incorrect or expired, the API may reject the request. Verify the token's validity.
  • Webhook URL Unreachable: If the webhook URL is not accessible or returns errors, events will fail to deliver. Ensure the URL is publicly reachable and responds correctly.
  • Missing Required Fields: Omitting the channel token or primary webhook URL will cause validation errors. Make sure these required fields are filled.
  • API Authentication Errors: Incorrect or missing API credentials will prevent successful requests. Confirm the API key is configured properly in n8n.
  • Timeouts or Network Issues: Network problems between n8n and NotificaMe Hub or the webhook endpoints can cause failures. Check connectivity and firewall settings.

Links and References

Discussion