---
title: "Use SLA actions with Jira automation"
canonical: "https://support.appfire.com/space/TTS/1464075666/Use%20SLA%20actions%20with%20Jira%20automation"
format: markdown
---
> Macro (aura-html)

The Trigger a Jira automation rule feature lets you use your SLA notifications to trigger Jira automation rules. For example, when an SLA is breached, you can automatically trigger a Jira automation rule to perform actions like adding comments to work items or creating incident reports.

This document provides step-by-step instructions on how to set up the integration between your Time to SLA notifications and Jira automation.

## Step 1: Create a Jira automation rule

Follow these instructions to create a Jira automation rule. For further details, refer to the [Atlassian documentation](https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Incoming-webhook). 

> 📝 Atlassian [is updating](https://community.atlassian.com/t5/Automation-articles/Update-on-Incoming-Webhooks-Trigger-for-Atlassian-Automation/ba-p/2921233) how incoming webhook triggers are routed. Any automation rules created before January 28, 2025, will continue to work until May 30, 2025, but must be migrated to the new endpoint to remain functional beyond this date. If you use incoming webhooks in your automation rules, we strongly recommend reviewing and updating them as needed.

1. Open the Jira space where you want to apply the rule.
2. Go to **Space settings** from the side menu.
3. Select **Automation** and click **Create rule **>** Create from scratch**.
4. Choose the **Integrations** category, then select **Incoming webhook as the trigger**.
5. Click **Next** and configure your needed actions. You can add multiple actions, such as sending comments, assigning work items, creating incidents, and more.

> 📝 Time to SLA provides various smart values to customize your actions dynamically. You can use:
> 📝 
> 📝 ```
> 📝 slaDescription: {{webhookData.slaDescription}}
> 📝 slaValue: {{webhookData.slaValue}}
> 📝 slaStartDate: {{webhookData.slaStartDate}}
> 📝 slaTargetDate: {{webhookData.slaTargetDate}}
> 📝 originStatus: {{webhookData.originStatus}}
> 📝 targetStatus: {{webhookData.targetStatus}}
> 📝 startConditions: {{webhookData.startConditions}}
> 📝 endConditions: {{webhookData.endConditions}}
> 📝 remainingDuration: {{webhookData.remainingDuration}}
> 📝 overdueDuration: {{webhookData.overdueDuration}}
> 📝 elapsedDuration: {{webhookData.elapsedDuration}}
> 📝 pausedDuration: {{webhookData.pausedDuration}}
> 📝 elapsedPercentage: {{webhookData.elapsedPercentage}}
> 📝 ```

6. Once you’re satisfied with your rule, click **Turn on rule**.
7. Jira will generate a unique webhook URL and a secret. Copy and save them for later.
8. Ensure the **Issues provided in the webhook HTTP POST body** option is selected.

In this example, we have set up a rule to send a comment utilizing parameters when it's triggered:

![Time to SLA Jira automation action configuration dialog](media://9e34da05-ec94-4dce-ac89-948327f3c95c)

## Step 2: Create a TTS notification

Next, configure a Time to SLA notification to link with your Jira automation rule.

1. Navigate to the SLA for which you want to add the notification.
2. Open the SLA’s settings, and click **Manage notifiers**.
3. Create a new notification by clicking **Add New SLA Notification**. If you don’t know how, follow the instructions on [this page](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/35881090/Set+a+Notifier+for+an+SLA?atl_f=PAGETREE).
4. For *When triggered...*, select **Trigger a Jira automation rule** as the action.
5. Paste the **Automation Webhook URL** and **Automation Webhook Secret** copied in [Step 1.7](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/1464075666/Use+SLA+actions+with+Jira+automation#:~:text=Jira%20will%20generate,Ensure).
6. Click **Save** to finish the setup.

Now, when the SLA is breached, the Jira automation rule will be triggered, executing the configured action (for example, `Add comment to work item`):

![Time to SLA Jira automation release note image showing rule configuration](media://b72075c8-c18e-48d7-a76e-fa584a521e0a)

## Jira automation usage limits

Time to SLA will attempt to trigger Jira Automation based on your configuration. However, remember that Jira automation may have usage limits or restrictions. If the automation does not trigger as expected:

- Refer to the [Jira automation documentation](https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Incoming-webhook) and [Automation service limits](https://support.atlassian.com/cloud-automation/docs/automation-service-limits/) to check for potential usage limits.
- Check your usage by opening the **Space settings**, and navigating to **Automation** > **Usage**.

> ⚠️ **Automation not triggering?**
> ⚠️ 
> ⚠️ If your Jira automation rule isn’t triggered by an SLA notification, this may be related to IP allowlisting in Jira Cloud. For more information, refer to our [FAQ](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/34932181/FAQ+SLAs#Why-isn%E2%80%99t-my-Jira-automation-rule-triggered-by-an-SLA-notification%3F).