Configuring Event Webhooks
  • 08 Apr 2025
  • 2 Minutes to read
  • Dark
    Light
  • PDF

Configuring Event Webhooks

  • Dark
    Light
  • PDF

Article summary

Before using a third-party event in a Workflow for the first time (or after its URL or signing secret changes), both Axonius and the vendor must be configured to exchange webhook events. Axonius needs to receive events and the vendor needs to send them.

Configuration Methods

Axonius can receive webhook events in two ways, depending on the vendor:

  • Product's adapter - Enable event collection directly in the product's adapter within Axonius.
  • Webhook URL and Signing Secret - The product must be configured in Axonius with a dedicated URL to receive Webhook events. If the product requires, also configure a signing secret. Ensure that this URL and signing secret are configured in the third-party vendor's webhook settings.
    • The URL is predefined and you cannot modify it.
    • The signing secret is used for security verification. Axonius and the vendor exchange this secret before event transmission to ensure events originate from a trusted source. If relevant, modify the Signing Secret.

Accessing Webhook Configuration

You can access and configure webhook details from:

Configuring the Webhook From the Workflow Event

Note:

For triggering Events, the link to the webhook configuration is under the Event name in the Trigger Type pane; for non-triggering Events, it's in the Event pane.

The following sections describe how to view, configure, and enable Event Webhook configurations:

Using Webhook URL and Signing Secret

Some third-party products require the Axonius dedicated Webhook URL and signing secret (if specified) before sending Webhook events to Axonius.

  • Viewing Configuration: When the Webhook URL and if relevant, the signing secret, are already configured in the product's Workflow Settings in Axonius, a message indicates that Webhook configuration is required for event collection.
    SlackMessageViewConfig.png

    1. Click View configuration.
    2. Verify that the URL and if relevant, the signing secret in the Webhook Configuration Details dialog are also configured in the vendor's settings.

    The following is the Webhook Configuration of the Slack Message event.
    SlackEventWHconfig.png

    1. If needed, modify the signing secret in both Axonius and the vendor's configuration.
    2. Click Enable Webhook.
  • Adding Signing Secret: When the Webhook URL is configured in the product's Workflow Settings, but the signing secret is missing, a pink message is displayed:
    CrowdstrikeWebhookIncomplete.png

    1. Click View Webhook Configuration.

    2. In the Webhook Configuration Details dialog, enter the signing secret.
      WebhookNoSigningSecret.png

    3. Ensure the URL and secret are also configured in the vendor's settings.

    4. Click Enable Webhook.

Enabling Events in the Product Adapter

Some third-party products require enabling event collection in the product's adapter (by default, disabled) before sending webhook events to Axonius.

  • Enabled Adapter: When Events are already enabled in the product's adapter (in Workflow Settings), a green message 'Event collection is enabled on the adapter' is displayed. The webhook is configured and the vendor can send events to Axonius.
    EventCollectionEnabled.png

  • Invalid Connection: When there is no valid adapter connection, a pink message is displayed:
    NoAdapterConnection.png

    1. Click View Adapter Settings.
    2. In the Adapter Settings page that opens in a new tab, click Add Connection, and configure a valid adapter connection.
  • Valid Connection, Events Disabled: When there's a valid adapter connection but events are not enabled for the adapter, a pink message is displayed:
    WorkDayEnableEventsWarning.png

    1. Click View Webhook Configuration.
    2. In the Adapter Events Configuration dialog that opens, select Enable events in adapter and click Apply.

AdapterEventsConfig.png



Was this article helpful?