> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # Auvik Webhook Setup Guide > Configure Auvik to deliver events to StackOne. ## Prerequisites Before continuing, you should have already completed the following for this connector: Enable the connector and set up its connector profile in your project. See Managing Connectors. Auvik - Basic Auth Connect an account using StackOne Hub or Auth Link. Auvik - Basic Auth

Copy your Native Webhook URL

In StackOne Hub, open this connection and copy the read-only Native Webhook URL. This is the per-connection HTTPS endpoint Auvik posts alert notifications to. It already contains the token that authorizes deliveries — copy it whole, exactly as shown, and treat it like a password.

Create the webhook integration in Auvik

The integration stores the URL Auvik posts to. Webhook integrations can only be created from the MSP dashboard, so check the site selector at the top left shows your MSP site rather than a client site.

In the side navigation under ADMIN, click Integrations. The OVERVIEW tab lists your existing integrations with their Name, Type and Enabled Status. Hover ADD INTEGRATION and choose Webhook from the menu.

Auvik Integrations overview page with the ADD INTEGRATION button highlighted

The ADD INTEGRATION menu lists every integration type Auvik supports — Autotask, ConnectWise Manage™, ServiceNow, Slack, Microsoft Teams, Opsgenie, iLert and others. Choose Webhook.

Add Integration menu expanded with the Webhook option highlighted

Complete the Add Webhook Integration form, then click Test Connection followed by Save.

  • Integration Name — a label for this integration, for example `StackOne`.
  • Webhook URL — paste the Native Webhook URL from step 1. It must be an HTTPS address.
  • Select your authentication method — leave No Authentication selected. The token already in the URL authorizes the delivery, so no extra credential is needed. Header, Basic Authentication and OAuth are also offered but not required.
  • Additional HTTP headers to send — leave the Key and Value fields empty.
  • Payload Transformation — leave Apply transformation here empty. StackOne expects Auvik's original alert format, and any Jsonata transformation here will stop events being recognised.
  • Test Connection confirms Auvik can reach the URL. It posts directly from this screen and does not use a notification channel, so a successful test does not yet mean real alerts will be delivered.
Add Webhook Integration form showing Integration Name and Webhook URL filled in, with the authentication and Payload Transformation sections below

Create a notification channel

The integration on its own is only a destination. A notification channel is what alerts actually send to.

Go to Manage Alerts and open the NOTIFICATION CHANNELS tab. It lists each channel with its Name and Contact Method. Click ADD NOTIFICATION CHANNEL.

  • SEND TEST ALERT on this screen sends a test through the channel itself, which is a better check than Test Connection because it exercises the channel too.
  • Creating the channel from the MSP dashboard makes it available to all client sites; creating it from a client's dashboard limits it to that client.
Notification Channels tab listing channels with the ADD NOTIFICATION CHANNEL and ASSOCIATE WITH ALERTS buttons highlighted

In the Add Notification Channel dialog, enter a Name, set Contact Method to Webhook, then choose the webhook integration you created in the dropdown that appears below it. Click SAVE.

  • The integration dropdown only appears once Contact Method is set to Webhook. Pick the integration by the Integration Name you gave it — this is what links the channel to your StackOne URL.
  • The Contact Method list also offers All User Emails, Custom Email(s) and Map.
Add Notification Channel dialog with Name, Contact Method set to Webhook, and the webhook integration selected below

Link your alerts to the channel

This is the step that decides whether anything is delivered. Creating the channel does not attach any alerts to it. Alerts that have never had their channel list edited inherit the channels defined at the root site, but any alert whose channels were changed at some point keeps its own list and ignores the root — so select the channel explicitly on each alert you want delivered.

Open Manage Alerts and use Search Alerts to find the alert you want delivered. Select its row, then click EDIT. The list shows each alert's Alert Name, Severity, Status, Description, Entities Applied To and Orgs Applied To.

Manage Alerts list of alert definitions with the EDIT button highlighted

In the alert's Notifications section each row holds one channel. Use the + beside a row to add another row, then pick your webhook channel in the new row and save the alert.

  • Alerts created in Alerts V2 keep their channel selection on the alert itself, so open them from the ALERTS V2 TABLE. The ASSOCIATE WITH ALERTS button on the Notification Channels screen applies to legacy alerts only.
  • Adding a channel in a new row leaves any existing channel in place; selecting a different channel in the same row replaces it.
  • ASSOCIATE WITH SITES under each row limits that channel to specific sites.
  • Auvik notes on this screen that an alert is created and visible in the All Alerts page even if no notifications are selected — so an alert showing in Auvik does not mean it reached StackOne.
Notifications section of an alert definition showing two channel rows with the plus and delete icons and ASSOCIATE WITH SITES links

Reopen the alert and read its Notifications section. The channels listed there are the alert's real destinations — if your webhook channel is not listed, the alert will not be delivered.

Notifications section of the saved alert listing both channels

Available webhook events

Auvik delivers one event type for everything. There is no per-event picker on the Auvik side — you choose which alert definitions are linked to the webhook channel, and every one of them arrives as the same event.

Alert notifications, delivered both when an alert starts and when it stops.

  • Alert Webhook (`alert`) — Fired when an alert condition becomes true, and again when it clears. Read `alertStatusString` on the payload to tell the two apart: `Triggered` when the condition starts, `Cleared` when it ends.

Auvik sends webhooks for alerts only.

  • Creating, changing or deleting a device, network, interface or configuration does not produce a webhook, and neither do new statistics.
  • A few alert definitions do detect change — such as Firmware Change on Network Element, Default Route Change, Configuration Backup and New Network Device Discovered — but they arrive as ordinary alerts carrying a text description rather than a list of changed fields.

Delivery format

Details of how Auvik delivers alerts to StackOne.

Each request carries a single alert as a flat JSON object — Auvik does not batch several alerts into one delivery. Timestamps on the payload are always UTC, regardless of the time zone set on your Auvik dashboard.

  • Alerts that apply to sub-items such as interfaces send one notification per sub-item by default, so a device with many affected interfaces produces many deliveries. The roll-up setting on the alert changes this to a single notification.
  • Auvik requires standard English characters in organization names; webhook alerts do not behave as expected if an organization name contains other characters.
## Verify Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.