> For the complete documentation index, see [llms.txt](https://docs.panther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.panther.com/alerts/destinations/torq.md).

# Torq Destination

## Overview

Destinations are integrations that receive alerts from rules, policies, system health notifications, and rule errors. Panther supports configuring [Torq](https://torq.io/) as the destination where you will receive alerts.

## How to set up Torq alert destinations in Panther

### Step 1: Create a Panther trigger in Torq

1. In your Torq console, navigate to **Integrations** > **Trigger** > **Panther**.
2. Click **Add**.\
   ![Under a "Panther" header, an "Add" button is circled.](/files/6ZOwvXzxRotYyczAw3hH)
3. In the **New Integration** pop-up modal, enter a descriptive **Integration Name**.\
   ![A "New Integration" title is above a text field labeled, "Integration Name." In the bottom-right corner, there are Cancel and Add buttons.](/files/PgrTBHzmQ6VbAwOsRbnP)
4. Click **Add**.
   * Copy the resulting **Endpoint** value and store it in a secure location, as you will need it in the following step.

     <figure><img src="/files/2eSVMszJ4lizZPC5R6kc" alt="A &#x22;Panther&#x22; header is above a table row with a &#x22;Panther&#x22; value for the &#x22;Name&#x22; column, and a URL value for the &#x22;Endpoint&#x22; column. The URL is circled."><figcaption></figcaption></figure>

### Step 2: Configure the Torq alert destination in Panther

1. In the left-hand navigation bar of your Panther Console, click **Configure > Alert Destinations**.
2. Click **+Add your first Destination**.
   * If you have already created Destinations, click **Create New** in the upper right side of the page to add a new Destination.
3. Click **Torq**.
4. Fill out the form to configure the Destination:
   * **Display Name**: Enter a descriptive name.
   * **Torq Webhook URL**: Enter the webhook URL you generated in Step 1.
   * **Severity**: Select the severity level of alerts to send to this Destination.
   * **Alert Types**: Select the alert types to send to this Destination.
   * **Log Type**: By default, we will send alerts from all log types. Specify log types here if you want to only send alerts from specific log types.
   * **Allow Manual Dispatch**: Set this toggle ON if you'd like to be able to [manually dispatch alerts](https://docs.panther.com/alerts#manual-alert-dispatch) to this destination.\
     ![A title says, "Configure your Torq Destination" and various fields are below it, including Display Name, Torq Webhook URL, and Severity.](/files/ccvnZn3eFTWjudIkTvKh)
5. Click **Add Destination**.
6. On the final page, optionally click **Send Test Alert** to test the integration. When you are finished, click **Finish Setup**.

## Additional Information on Destinations

For more information on alert routing order, modifying or deleting destinations, and workflow automation, please see the Panther docs: [Destinations](https://docs.panther.com/destinations).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.panther.com/alerts/destinations/torq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
