Setup time: 6 Min
Maximize your team’s efficiency with All Quiet’s outbound webhooks. Connect seamlessly with third-party platforms, enabling real-time alerts and maintaining operational awareness.

​
Create Outbound Integration

  1. Click on Integrations > Outbound to navigate to the outbound integrations page.
  2. Once you’re on the Outbound Integrations page, click on Create New Outbound Integration in the top-right corner.
  1. Enter a name for your integration in the Display Name field, such as “My Outbound Webhook”.
  2. Select a team from the dropdown menu.
    For Organizations with Pro and Enterprise plan: This is going to be the root team of your integration. You will be able to add additional teams that will be able to use the Webhook in the next step.
  3. In the Type section, choose Discord from the dropdown menu.
  4. After filling in all required details, click on the Create Integration button to finalize the setup.
After successfully creating your new outbound integration, you’ll be redirected to the details page automatically.
    • The option Trigger Always is enabled by default. This means that we will forward all incidents to your Webhooks, unless excluded by additional advanced routing rules.
    • When selecting Trigger Always After Forwarding, we will not automatically send incidents to your Webhooks. Requests will only be sent if users manually forward specific incidents or if you set up advanced routing rules for your Webhook Outbound integration that automatically forward incidents in specific scenarios. After Forwarding, all updates of the incident will also be pushed to the Outbound Webhook.
    • When selecting Trigger Only On Forwarding, we will only forward a snapshot of the current incident history to your Outbound Webhook in the moment users manually forward specific incidents or if you set up advanced routing rules for your Webhook Outbound integration that automatically forward incidents in specific scenarios. We will not send any incident updates to the Outbound Webhook afterwards.
    • You can change your selection anytime.
  2. Only for Pro and Enterprise plan: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an admin in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.

​
Configure Webhook Request

To configure webhook requests in the All Quiet incident management tool, you would typically follow these steps:
  • Load an Incident: Choose an incident from your list to serve as a test case.
  • Write a Template: Craft a Handlebars template that converts the incident data into a webhook request payload.
  • Review & Dispatch: Examine the generated request for accuracy, then save and trigger a test request to confirm the integration works as expected.

​
Load Incident Model for Testing

  1. Select an incident from the ‘Latest Incidents’ section. This incident acts as a sample to define how the webhook should behave.
  2. Clicking on an incident will populate its JSON structure in the test area (2), allowing you to use real incident data to model the webhook request.

​
Write a Template

With the incident data loaded, navigate to the ‘Template’ section. Here, use Handlebars syntax to map the incident data fields to the corresponding webhook JSON structure. This template determines how the incident data is transformed into the format required by the receiving endpoint. The following JSON structure provides a template for sending a webhook request. You can modify the method, url, headers values, and the body content to fit the specific requirements of your webhook integration. For each new incident event, such as creation, resolution, or commenting, All Quiet will send an HTTP call with the specified method, headers, and body to the URL defined in the webhook request JSON. 
{
    "method": "POST",
    "url": "https://your-url.com",
    "headers": {
        "Content-Type": "application/json; charset=utf-8",
        "X-Your-Header": "abc"
    },
    "body": {
        "text": "Your Text Content",
        "formData": {
            "key1": "a",
            "key2": "b"
        },
        "json": {
            "prop1": "a",
            "prop2": {
                "someArray": [{"k": "v"}]
            }
        }
    }
}
Only one of text, formData, and json is used. If you specify more than one, the first one is used.

​
Outbound IP Addresses

The outbound IP addresses used for webhook requests are dynamic and can be retrieved from the following endpoints: While these IP addresses are generally stable, we do not guarantee their persistence. It’s recommended to regularly check these endpoints for any changes.

​
Inspect and Send Webhook Request

  1. In the ‘Webhook Request’ section, review the final payload based on your template. This is where you ensure that all necessary data is correctly formatted and included.
  2. After confirming the request is accurate, save the mapping.
  3. Use the Trigger Dummy Request button to test the webhook, validating the end-to-end process.
  4. The recorded request and response will be visible in the right pane under “Latest Requests”.
You now integrated outbound webhooks with All Quiet, simplifying incident management by consolidating notifications and actions in your place of choice.

​
Update / Patch Incidents via Outbound Webhook

In addition to only sending an All Quiet incident to another tool via the Outbound Webhook, you can also use it to patch (update) the incident directly. This can be valuable when you want to trigger a certain action or when you simply want to enrich the incident by sending it to your Outbound Webhook. To allow incident patching via Outbound Webhook
  1. Adjust your Outbound Webhook’s request template and add "enableIncidentUpdates": true.
  1. Prepare a patch response from the URL you’re sending the incident to. Find a few examples for patches below. The whole list of patches we allow can be retrieved via our Public API Documentation,“IncidentResource” Patch.