Overview
Axonius workflows can be triggered or continued by events from external third-party systems.
Before you can use third-party events in workflows, Axonius must be configured to receive webhook events from their vendors.
The Settings> External Integrations> Workflows Events page provides the necessary configuration for Axonius to receive Webhook Events from each third-party product.
The method for configuring webhooks varies depending on the third-party product.
You can also configure webhook settings directly from the workflow Event pane. Learn how to configure the webhook from the workflow event.
Webhook Configuration Methods
The following are the webhook configuration methods:
-
Webhook URL and Signing Secret - Some products require you to provide Axonius's webhook URL, dedicated to that product, and a signing secret for security verification. Note that not all products require a signing secret.
-
Adapter Event Enablement - Other products require you to enable event collection directly within their Axonius adapter.
For detailed instructions on configuring webhook settings for specific third-party products, refer to the Events library.
Configuring Webhook Settings for a Product
To configure a product's Webhook settings
-
From any page, in the top right corner, click the Settings icon
. The System Settings page opens.
-
In the System Setting's navigation pane, expand External Integrations and select Workflows Events.
-
In the Workflows Events page, from the Select Product dropdown, choose the desired third-party product (vendor).
-
Depending on the Webhook configuration that opens for the product:
Using the Webhook URL and Signing Secret
Some third-party products require the Axonius dedicated Webhook URL and signing secret (if specified) configuration before sending Webhook events to Axonius.
To view or configure the product's Webhook settings
-
Copy URL: The Axonius URL displayed is read-only and is the destination for incoming webhook events. Click the Copy icon to copy this URL and paste it into the vendor's configuration.
- Exception: The Microsoft Teams webhook URL does not need to be manually pasted into its configuration. When a user clicks a response button in a message sent with the Microsoft Teams - Send Message interactive enforcement action, this URL is automatically sent to the enforcement action. The Response event is then sent to this URL. Learn more on the Teams Message Response configuration.
-
Manage Signing Secret: Enter or update the signing secret (if required). Axonius exchanges the signing secret with the third-party vendor to verify the authenticity of webhook events. This secret is vital for security. Save this value for future reference. If you need to enter or update the signing secret, enter the new value, and then click Save.
For example, the Slack Webhook settings display both the Webhook URL and the Signing Secret.
Enabling Events in the Product Adapter
Some products require enabling event collection in the product's adapter (by default, disabled) before sending webhook events to Axonius.
To enable events in the product's adapter
- In the Workflows Events screen, select the Enable events in adapter checkbox.
- Click Save.
For example, the ServiceNow event uses these settings.