---
title: "Create notifications"
canonical: "https://support.appfire.com/space/TTS/46465066/Create%20notifications"
format: markdown
---
> Macro (aura-html)

With Time to SLA, you can configure notifications to reach the right people at the right time. Use notifications to alert your team before an SLA is breached so they can take action in time. If an SLA is breached, send automated reminders to keep tasks on track until they are completed.

## Prerequisites

- Before you create a TTS notification, make sure you have permission to access the issues included in the SLA. The person responsible for creating the notification must have the necessary authorization to access the relevant issues related to the scope of this SLA.

## Steps

1. Open the **SLAs** page.
2. Click **Notifications** (bell icon) on the row of the SLA for which you want to set up a notifier.
3. Click **Add New SLA Notification**. The *SLA Notification* dialog appears.
4. If you want repeated notifications at regular intervals, select when you want to be notified and when to stop receiving repeated notifications. Choose one of the following triggers:
  - **is breached –** you’ll receive a notification when the SLA is breached.
  - **will be breached in – **you'll be able to get notifications before the Target Date is reached. TTS uses this value to send a notification before the SLA Goal is met. For example, if you enter 1h, you'll be notified 1 hour before the Target Date is reached.
  - **has been breached for – **you’ll receive a notification when your SLA has been breached for the time period you’ve chosen.
  - **has reached – **you’ll be notified when SLA reaches the percentage you’ve chosen. For example, if you enter 90% as the SLA Goal Ratio, the notification will be sent when 90 percent of the SLA goal has elapsed.
  - **is over – **you’ll be notified when the SLA is finished.

> 📝 All time values must be in the Jira time format *(for example, *`1d 2h 30m`*).*

5. Check the **Repeat every...** box to get notifications at the intervals you define.
6. Check the **Stop repeating after...** box to stop sending notifications after a certain number of notifications are sent.
7. **Enable** **working calendar** is automatically selected for new notifications.
  - With this option **selected**, Time to SLA calculates notification offsets and repeat intervals using the SLA’s working calendar, excluding non-working hours, weekends, and holidays.
  - With this option **deselected**, Time to SLA calculates notification timing as continuous elapsed time (24/7). Non-working hours, weekends, and holidays are included. Notifications can be triggered outside of working hours.
  - Note: The **Enable working calendar** setting impacts notification timing only. It does not change the SLA goal or working calendar, and existing notifications retain their saved setting.
8. Select the action TTS should take when the notifier is triggered. TTS can:
  - **Send an email –** You can customize the subject and content of the email using dynamic parameters with `$`. Afterward, you can choose the recipients or add custom recipients. TTS offers a flexible way of creating dynamic email content. [This page](https://appfire.atlassian.net/wiki/spaces/TTS/pages/46727214) lists the notification parameters you can use.
  - **Fire an event –** If you want to fire an event, select it here. The issue's selected event will be fired at the time of notification.
  - **Send a Slack message –** Add the Slack webhook URL and, optionally, customize the Slack message.

> 📝 **To find or create a Slack channel webhook URL, follow these steps:**
> 📝 
> 📝 1. **Create a Slack app**:
> 📝   - Navigate to the [Slack API: Your Apps](https://api.slack.com/apps) page.
> 📝   - Click **Create an App**, and select **From scratch**.
> 📝   - Provide a name for your app, and select the workspace where you want to post messages.
> 📝 2. **Enable Incoming Webhooks**:
> 📝   - Go to the **Incoming Webhooks** in your app's settings.
> 📝   - Toggle the **Activate Incoming Webhooks** switch to **ON**.
> 📝 3. **Generate a Webhook URL for a channel**:
> 📝   - Click **Add New Webhook to Workspace**.
> 📝   - Select the channel where the app will post messages.
> 📝   - Click **Allow** to authorize.
> 📝   - After authorization, you'll receive a unique webhook URL in the format `https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX` that you can copy and paste into the Slack message field in TTS.
> 📝 
> 📝 For more details, refer to [Slack’s Incoming Webhooks documentation](https://api.slack.com/messaging/webhooks#create_a_webhook).

9. Click **Save**.

After you've saved your notification, you can use the **Notifications** page to edit, clone, or delete your notifications. From there, you can associate your notifications with different goals as well.

![Notifications page listing configured SLA notifications with options to edit, clone, delete, and associate notifications with goals.](media://b82f39ec-7e89-4492-9bef-ef20316f2b37)

> ℹ️ **Associate with goals**
> ℹ️ 
> ℹ️ If an SLA has multiple goals, you can use this feature to configure distinct notifications for each goal. This flexibility lets you tailor notifications based on specific requirements, such as priority or response time.
> ℹ️ 
> ℹ️ **Example**
> ℹ️ 
> ℹ️ Imagine you have an SLA with the following goals:
> ℹ️ 
> ℹ️ - **High-priority issues**: 1 hour
> ℹ️ - **Low-priority issues**: 24 hours
> ℹ️ 
> ℹ️ In this scenario, you may want to send notifications more frequently for critical issues and notify different users based on the issue's priority.
> ℹ️ 
> ℹ️ ![Notifications page showing the Associate with goals option for an SLA notification.](media://f421b9de-f099-4f91-9701-9538b9fe291d)
> ℹ️ 
> ℹ️ The **Associate with goals** feature makes this possible by allowing you to link specific SLA goals to customized notifications, ensuring the right information reaches the right people at the right time.