Skip to main content

​
Overview

A webhook sends information to an external URL when a selected event occurs in Nexudus. Use webhooks when another system needs to react to activity in your location without repeatedly checking Nexudus for changes. Go to Settings → Integrations → Webhooks. You need the webhook permission or administrator access.

​
Before you start

  • Confirm the receiving service can accept HTTPS requests.
  • Obtain the exact URL and the event type it expects.
  • Agree with the receiving-system owner how failures will be monitored and handled.

​
Create a webhook

1

Open Webhooks

Go to Settings → Integrations → Webhooks and add a webhook.
2

Name the webhook

Use a clear internal name, such as “Send new reservations to CRM”.
3

Choose an action

Select the Nexudus event that should trigger the notification.
4

Enter the destination URL

Enter the secure URL provided by the receiving system.
5

Activate and monitor it

Save the webhook, activate it, then verify the first event reaches the destination.

​
Field reference

Webhooks belong to one location. A webhook added at your network location doesn’t apply to your other locations.

​
Monitor delivery

Review Last trigger, Last error, and Error count after setup and whenever the receiving system changes. Deactivate the webhook before replacing an outdated URL so failed deliveries do not continue. If the receiving system fails to accept a request, Nexudus tries again several times, waiting longer between each attempt. A successful delivery resets the error count. After more than 10 failures in a row, the webhook is turned off — fix the receiving system, then turn Active back on.

​
Verify requests come from Nexudus

To let the receiving system check that requests really come from Nexudus, set a Shared secret in Settings → Integrations → Webhooks. Every webhook request then carries an X-Nexudus-Hook-Signature header: the HMAC-SHA256 of the raw JSON body, keyed with your secret, in hexadecimal. The receiving system computes the same value and compares it with the header. The signature is computed from ASCII bytes by default. If the receiving system hashes UTF-8 — and signatures fail on text with accents or symbols — turn on Use UTF8 encoding. The shared secret also signs requests from automation tiles that call a URL.
Webhook URLs can give an external system access to operational data. Use a trusted HTTPS endpoint and avoid placing credentials directly in the URL unless the receiving system explicitly requires it.