# Set up Jira to Receive Radiant Outgoing Webhooks

This guide will walk you through creating an automation rule in Jira that listens for incoming webhooks from Radiant and creates a corresponding Jira issue (Ticket, Bug, or Incident) with all the relevant alert details.

### Prerequisites

Before you begin, ensure you have the following:

* [ ] Admin access to Jira
* [ ] The specific Jira project (and its Key, e.g., `SEC`, `OPS`) where you want the tickets to be created
* [ ] Understanding of [Radiant Outgoing Webhooks](/export-logs/outgoing-webhooks/set-up-outgoing-webhooks.md)

### Create the incoming webhook trigger in Jira

First, you need to generate a secure webhook endpoint in Jira that Radiant can talk to.

1. In Jira, navigate to **Project settings > Automation** (for a specific project) or **System > Global Automation** (to create a rule that works across multiple projects).
2. Click **Create rule** in the top-right corner.
3. Under **Add a trigger**, search for and select **Incoming webhook**.

<div align="left"><figure><img src="/files/P4ZkMfj1XdRyEFTfo2Fv" alt=""><figcaption></figcaption></figure></div>

4. Under **Execute this rule using** select **Issues provided in the webhook HTTP POST body**.
5. Under **Rule details**, select an action for your rule (e.g., Create Incident, Create sub-tasks), as well as any conditions or branches you may want to add.

<figure><img src="/files/hCq5qX9uBPL9PCQA0e58" alt=""><figcaption></figcaption></figure>

6. Ensure **Turn on rule** is toggled. Give the rule an identifiable name and configure the necessary edit permissions.&#x20;

<div align="left"><figure><img src="/files/2XvCd3VTgJHnXsQ7k1yK" alt="" width="375"><figcaption></figcaption></figure></div>

7. You will see a unique **Webhook URL** and a **Secret** key. Copy both of these values and save them temporarily; you will need them for the Radiant configuration.

<figure><img src="/files/kQb1YQ5yCKl7FL9vlR7Y" alt=""><figcaption></figcaption></figure>

### Configure the automation rule to create tickets

1. In the rule builder, click **+ Add component.**
2. Select **THEN: Add an action.**

<div align="left"><figure><img src="/files/Aec91LESTLkSAJbx1Gzs" alt="" width="375"><figcaption></figcaption></figure></div>

3. Search for and select **Create issue.**
4. Choose the target project and type (e.g., Task, Incident, Bug).
5. Map the data sent by Radiant to your Jira fields using **Smart Values**.

### Recommended field mappings

Copy and paste the following Smart Values into your Jira fields to populate them with Radiant data:

**Summary**

```css
Radiant Security Alert: {{webhookData.rs_alertNumber}} - {{webhookData.rs_webhookTriggerType}}
```

**Description**

```css
h3. Alert Details
* *Alert Number:* {{webhookData.rs_alertNumber}}
* *Trigger Type:* {{webhookData.rs_webhookTriggerType}}
* *Time:* {{webhookData.rs_webhookTriggerTimestamp}}
* *Link to Radiant Alert:* [View Analysis|{{webhookData.rs_alertUrl}}]

h3. Summary
{{webhookData.rs_alertBrief.summary}}

*Intent:* {{webhookData.rs_alertBrief.intent}}

h3. Raw Payload
{{webhookData}}
```

**Labels:** e.g. `radiant`, `soc-automation`, `auto-ticket`

#### Optional: Map "Priority"

You can also map the Jira Priority field based on the Radiant `rs_webhookTriggerType`.

1. In the rule builder, click **+ Add component** (after the "Create issue" step).
2. Select **IF: Add a condition.**

<div align="left"><figure><img src="/files/6ly9CKeVNWt0iCBJkVQw" alt="" width="375"><figcaption></figcaption></figure></div>

3. Under **Add a condition**, select **{{smart values}} condition.**
4. Configure the Condition:
   * **First value**: Paste `{{webhookData.rs_webhookTriggerType}}`
   * **Condition**: Select `contains`
   * **Second value**: Enter `Malicious`
5. Click **Next.**
6. Now, inside this new **If block**, click **+ Add component** > **THEN: Add an action.**
7. Select **Edit issue.**
8. Check the **Priority** field and set it to **High** (or your preferred Critical status).
9. Click **Next.**

{% hint style="info" %}
**How this works:** The rule will first create the ticket with the standard description. Then, it checks if the alert is "Malicious"; if true, it immediately updates that same ticket to "High Priority."
{% endhint %}

### Configure a Radiant outgoing webhook

To configure the webhook, please refer to the [Set up Outgoing Webhooks](/export-logs/outgoing-webhooks/set-up-outgoing-webhooks.md) guide.

{% hint style="danger" %}
**Important note:** When configuring the Jira webhook in Radiant, the **Header Name** *must be exactly***:**\
\&#xNAN;**`X-Automation-Webhook-Token`**

This is the header Jira Automation expects for authenticating incoming webhook requests.\
Using anything else (e.g., `Authorization`, `X-Radiant-Token`, etc.) will cause Jira to reject or ignore the webhook.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.radiantsecurity.ai/export-logs/outgoing-webhooks/set-up-jira-to-receive-radiant-outgoing-webhooks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.