Nexudus can communicate with other systems and automatically push data on to those systems when specific actions take place. This information is transferred over the internet by means of webhooks. The receiving end of these webhooks is normally a system that understands this data and is able to process it.
The receiving end of a webhook will listen for incoming calls from Nexudus with specific data. For example, if you want to notify another system every time you make a change to a member or contact you could use the "Coworker Update" webhook which sends the data of the contact or member whose record you have updated.
Webhooks are created from the Settings > Integrations menu. We keep adding new webhooks as users require them for specific integrations but these are the ones we have available so far:
Send Welcome Email
Coworker Contract Activate
Coworker Contract Cancel
Coworker Contract Renew
Coworker Contract Upgrade Downgrade
Coworker Contract Activate First
Coworker Invoice Create First
Coworker Invoice Create
Coworker Invoice Delete
Coworker Invoice Update
Coworker Invoice Refund
Coworker Invoice Credit Note
Coworker Invoice Paid
Coworker Invoice Failed Payment
Coworker Invoice Received Payment
Coworker Invoice Awaiting Payment
Calendar Event Create
Calendar Event Update
Calendar Event Attendee Delete
Calendar Event Attendee Create
Calendar Event Attendee Update
Global Chat Message Create
NewsLetter Subscriber Create
NewsLetter Subscriber Subscribed
NewsLetter Subscriber UnSubscribed
NewsLetter Subscriber Removed From Group
Coworker Checkin Failed
Community Board New Thread
Community Board New Reply
Visitor Checked in
Blog Post Delete
Calendar Event Delete
HelDesk Message Created
HelpDesk Comment Created
Coworker Message Create
Webhook requests created by our servers can be verified by calculating a digital signature using a shared secret you can type in Settings > Integrations.
If a shared secret is available, each Webhook request includes a X-Nexudus-Hook-Signature header which is generated using the app's shared secret along with the data sent in the request.
To verify that the request came from Nexudus, compute the HMAC 256 digest and compare it with the value in the X-Nexudus-Hook-Signature header. If they match, you can be sure that the Webhook was sent from Nexudus and the data has not been compromised.