# 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 with permission to create Automation Rules in your Jira project or Global settings.
* [ ] The specific Jira project (and its Key, e.g., `SEC`, `OPS`) where you want the tickets to be created.
* [ ] Understanding of [Radiant Outgoing Webhooks](https://help.radiantsecurity.ai/export-logs/outgoing-webhooks/set-up-outgoing-webhooks).

### 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2F6ymd9GbiiwuLg5Pmzum8%2FSet%20Up%20Jira%20to%20Receive%20Radiant%20Outgoing%20Webhooks_01.jpg?alt=media&#x26;token=dabcdb9c-8084-4467-bc8c-b4b95993ab53" 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2FsLhG5PxjrizxYUrqn2LQ%2FJira_03.png?alt=media&#x26;token=90a8266e-3f04-45f1-b6be-509bd5d08fdb" 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2F8whB2v0Pftylk3kAj5Yd%2FJira_04.png?alt=media&#x26;token=f200269f-25f8-4dfe-8f7b-8095369a3433" 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2F6sub3A3sbp3EVnqCIDTH%2FSet%20Up%20Jira%20to%20Receive%20Radiant%20Outgoing%20Webhooks_04.jpg?alt=media&#x26;token=ecc781fb-9b2a-49f6-ada1-a5887c499fcd" 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2FLK2AZK8obOU44islc9S8%2FSet%20Up%20Jira%20to%20Receive%20Radiant%20Outgoing%20Webhooks_05.jpg?alt=media&#x26;token=33bf02e6-eee4-46f5-8e5a-caf11c6ff129" 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="https://2439665791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPsFulb2ZOtSPcRSc2rXE%2Fuploads%2FX8IkZMjMvWln1o5RK7Be%2FJira_06.png?alt=media&#x26;token=d70565d2-fc41-45ce-903c-437907856542" 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](https://help.radiantsecurity.ai/export-logs/outgoing-webhooks/set-up-outgoing-webhooks) 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 %}