How to configure Webhooks Integration in Hexnode UEM?

What are webhooks in Hexnode UEM?

A Webhook is an event-driven mechanism that automatically sends real-time data from Hexnode UEM to external applications. In Hexnode UEM, an event represents a specific activity or status change associated with the endpoint—such as a compliance failure, app installation error, or a low battery state.

While Hexnode UEM traditionally delivers Alert Profiles via Email or SMS, Webhook Integration provides a flexible, programmatic third channel. It allows you to push alert payloads directly to platforms like Microsoft Teams, Slack, or enterprise IT Service Management (ITSM) and Security Information and Event Management (SIEM) systems.

Before you begin

To successfully configure a webhook, ensure you have:

• Administrative access to the Hexnode UEM portal.
• Permissions in the target application (e.g., Microsoft Teams, Slack, or your custom server) to generate an incoming webhook URL.
• The generated HTTP POST URL from your target application. You will need to securely paste this URL into Hexnode UEM for the integration.

How webhook delivery works

The webhook integration relies on a straightforward sequence to deliver information:

1. Trigger: A specific activity occurs (e.g., a device falls out of compliance) across the endpoint or in the Hexnode UEM console.
2. Match: Hexnode UEM checks if this activity matches the conditions defined in an active Alert Profile.
3. Package: If a match is found, Hexnode UEM packages the alert details (like the time, event description, and portal information) into a JSON payload.
4. Delivery: Hexnode UEM sends this payload via an HTTP POST request to the destination URL you configured.
5. Receipt: The target application receives the payload and displays it to the channel members or processes it within the ITSM tool.

Add a new webhook

1. Log in to the Hexnode UEM portal.
2. Navigate to Admin > Webhook.
3. Click on Add New to initiate the configuration.

Configure the webhook

In the Add Webhook window, populate the following fields:

• Name (Required): Enter a unique, identifiable name for this connection (e.g., “Security Alerts to Teams”).
• Description: Add optional context about the purpose of this webhook.
• URL (Required): Paste the destination HTTP POST URL generated by your target application. This is the exact address where Hexnode UEM will deliver the JSON payload.
• Timeout (in seconds): Define the maximum time Hexnode UEM should wait for the target application to acknowledge receipt of the payload. If the target server does not respond within this window, the delivery fails.

Select an authentication method

Authentication ensures your target application can securely verify that the incoming alert data is genuinely from Hexnode UEM. Select the method required by your target application:

• No authentication: The receiving application does not require credentials to accept the payload. (Commonly used for standard Slack or Teams webhook URLs).
• Basic authentication: Requires a standard Username and Password.
• Access token: Uses a token-based security approach. If selected, choose the specific format expected by your target application:
  • Bearer: The standard OAuth token format.
  • Basic: Passes the token as a base64-encoded string.
  • Custom: Passes the token without standard prefixes.
  • None: Sends the token value directly with no specific authentication scheme attached.

Test the webhook

Before saving, click the Test button at the bottom of the configuration window.

Hexnode UEM will send a sample payload to your configured URL. Check your target application to confirm receipt. For example, a successful test sent to Microsoft Teams will appear in the channel as a message stating: “Webhook test successful from Teams check“.

Save the webhook

Once the test is successful, click Save. The webhook is now stored in your Hexnode UEM portal, but it will not send live alerts until it is linked to an Alert Profile.

Link the webhook to an Alert Profile

To activate automated alerts for specific events, you must define the triggers that initiate the payload delivery.

1. Navigate to Admin > Alert Profiles.
2. Click Add New (or select an existing profile to edit).
3. Configure your desired conditions (e.g., Device Compliance, Battery Level).
4. Proceed to Step 2: Actions.
5. Locate the Webhooks section alongside the Email and SMS options.
6. Select your newly saved webhook from the dropdown menu.
7. Click Save on the Alert Profile.

Verify a live event

Once the webhook is linked to an active Alert Profile, trigger a live event that matches your configured conditions (for instance, generating a new API key).

Check your target application. The payload will deliver the specific details of the event. For example, a live console event alert in Teams will display context such as the event subject (“API key generated“), the specific portal (admin-console.hexnodemdm.com), and the exact timestamp.

Edit or manage the webhook

If you need to update the destination URL, change the authentication token, or modify the timeout settings:

1. Navigate to Admin > Webhook.
2. Click on the name of the existing webhook.
3. Click Edit, make your necessary changes, and click Save.

What to do next

To generate the required destination URL for the URL field, refer to the platform-specific configuration guide for your target application:

• Send Hexnode UEM alerts to Microsoft Teams using webhooks
• Send Hexnode UEM alerts to Slack using webhooks
• Send Hexnode UEM alerts to a custom webhook endpoint