HTTP Server - Send to Webhook
  • 20 Nov 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

HTTP Server - Send to Webhook

  • Dark
    Light
  • PDF

Article summary

NOTE
This Enforcement Action was formerly named Web Server Information - Send to Webhook.

HTTP Server - Send to Webhook serializes the entities retrieved from the saved query supplied as a trigger (or entities selected in the asset table) as JSON. This JSON data will be sent to a configured webhook. When used with a saved query as a trigger, only the fields configured in the saved query are added to the JSON.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

Note:

Required Fields

These fields must be configured to run the Enforcement Set.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

  • Webhook URL - Specify the webhook URL.
  • Custom format for body (use {$BODY} as keyword) (default: {"entities": {$BODY}}) - You can customize the webhook body.
    • Use {$BODY} to include the entities found in the saved query supplied as a trigger (or entities that have been selected in the asset table) data.
    • Use {$BODY_ESCAPED} instead of {$BODY} if you want to escape JSON characters so that the JSON is sent as a string instead of an object.
  • Connection timeout (seconds) (required, default: 10 seconds) - Define the number of seconds before the attempt to connect to the webhook is considered to be timed out. As a result, the enforcement action execution will fail.
  • Writing data to webhook timeout (seconds) (required, default: 1200 seconds) - Define the maximum number of seconds before the attempt of completing sending the data to the webhook is considered to be timed out. As a result, the enforcement action execution will fail.
  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.

  • Authorization header user name and authorization header password (optional, default: empty) - Specify authorization header user name and password, if required.

    • If supplied, Axonius will pass the specified authorization header information along with the Webhook URL.
    • If not supplied, Axonius will not pass any additional information along with the Webhook URL.
  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTP proxy - When a proxy is supplied, Axonius will use the proxy, instead of the direct URL, when connecting to the HTTP Webhook URL.

  • Additional headers (optional, default: {"Content-type": "application/json"}) - Add Customized Headers to be Sent with Request. For Example:

    {"Content-type":"application/json","Accept":"application/json","Authorization":"Bearer <TOKEN>"}

  • Gateway Name - Select the Gateway through which to connect to perform the action.


For more details about other Enforcement Actions available, see Action Library.




Was this article helpful?