# Actions Each Workflow has a set of predefined actions that guide how it moves forward. These actions can involve tasks like attaching Runbooks or marking an incident as SLO-affecting. {% hint style="info" %} **Note:** * Each action will be executed serially, and all actions executed by a Workflow will be recorded in the Incident timeline. * The Workflow will continue to run irrespective of the success/failure of a specific action. {% endhint %} ## Squadcast Actions Here are the steps to set up each of the supported Squadcast actions: {% hint style="info" %} The below templating variables can be used for almost all actions however they will return values only if the trigger is "When Incident Note is added" otherwise it will be empty. ```mustache incident_last_note.note incident_last_note.user_name incident_last_note.user_email ``` {% endhint %} ### Attach Runbook(s) To include attaching runbooks as an action, 1. Click on the Squadcast logo under **Select to add action**. -> In the side panel, click on **Attach Runbook(s)**. 2. From the list, search and select one or more runbooks to attach. -> Click on **Attach**. This process will automatically attach the selected runbook(s) to your incident.

Image. Select one or more runbook(s) to attach

### Add Communication Channel To specify adding a communication channel as an action, 1. Click on the Squadcast logo under **Select to add action**. -> In the side panel, click on **Add Communication Channel**. 2. Choose the type of channel you want to add. -> Input the **link** and *optional* **text to display** for your Communication Channel. 3. You can include multiple communication links -> Lastly, click **Save**. This action directly adds communication details to your communication card of the Incident.

### Add Incident Note To include adding an incident note as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Add Incident Note.** 2. Type in the note you want to add -> And, click **Save.** This action automatically adds a note to the incident.

### Mark Incident as SLO affecting To include marking incidents as SLO affecting as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Mark Incident as SLO Affecting.** 2. Select an **SLO** from the drop-down -> Select **one or more SLIs** from the other drop-down -> Click **Save**. This action will automatically mark the incident as SLO-affecting. {% hint style="warning" %} **Important:** When selecting the "Mark Incident as SLO Affecting" action, please ensure that you choose an active SLO that is associated with the same service as your incident. {% endhint %}

Image. Mark the Incident as SLO Affecting

### Make an HTTP call To include making an HTTP call as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Make an HTTP call.** 2. Enter the **URL** where you want to make the HTTP call -> Select the **HTTP method** from the dropdown. Available methods are GET, POST, PUT, PATCH, and DELETE. The payload will be sent to the URL endpoint that is added. 3. Next, you can configure **additional headers**. These headers will get attached to all the API calls that will be made using this workflow. 4. Then, you can configure your payload. It supports templating variables and string concatenation.\ \ Here is the list of supported variables: * incident\_status * incident\_message * incident\_description * service\_id * service\_name * alert\_source\_type * alert\_source\_short\_name * payload These variables can be accessed by appending `event.`in beginning. For instance, `event.incident_message` 4. Once you have entered all the details, click **Save**. This action automatically makes a custom HTTP call when the trigger conditions are met. {% hint style="info" %} **Note:** The success/failure along with the response will be stored in the workflow logs. {% endhint %}

### Send an Email This action automatically sends an email to one or more addresses given when the trigger conditions are met. To include sending an email as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Send an Email.** 2. Type in the following details: * Email Address: You can add multiple emails here with a space in the middle. * Subject and Body: You can utilize templating variables for the subject and body of the email. Here is the list of the supported templating variables: ``` incident_id incident_status incident_message incident_description service_id service_name alert_source_type alert_source_short_name payload ``` \ It will be utilized as such: Message: `{{event.incident_message}}` 3. Once you have entered all the details, click **Save**.

### Trigger Manual Webhook This action automatically triggers the pre-configured manual webhook. To include triggering a manual webhook as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Trigger Manual Webhook.** 2. Next, select the webhook to trigger from the dropdown. 3. Once the webhook is selected, click on **Save**.

### Update Priority This action automatically updates the priority of an incident. To include updating priority as an action, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Update Priority.** 2. Next, select the priority level from the dropdown. 3. Once done, click on **Save** to complete adding the action.

### Add Status Page Issue This action automatically creates an issue in the StatusPage for the incident. To create a status page issue, 1. Click on the **Squadcast logo** under Select to add action -> In the side panel, click on **Add Status Page Issue**. 2. Select the status page you want to update -> Enter the **Issue Title** and select the **Page Status** from the drop-down menu. 3. Next, select the **Component and related Impact**. Enter the **Issue Status** and its respective **Message**. 4. Once done, click on **Save** to complete adding the action. ## Slack Actions Here are the steps to set up each of the supported Slack actions: ### Create Incident-Specific Slack Channel This action automatically creates a dedicated Slack channel for the incident. To create an incident-specific Slack channel, 1. Click on the **Slack logo** under Select to add action -> In the side panel, click on **Create Incident-Specific Slack Channel**. 2. Next, select between the two given options. 1. You can choose to assign an auto-generated name to the Slack channel. The format used here would be `sq--` 2. Or you can choose to assign the name in this specific format by entering it in the field below.\ \ This option supports templating variables, for the ones shown below: ``` incident_id incident_status incident_message incident_description service_id service_name alert_source_type alert_source_short_name payload ``` \ It will be utilized as such: Message: `{{event.incident_message}}` {% hint style="info" %} **Note:** We will utilize only the initial 35 characters from these templates. {% endhint %} 3. Once done, click on **Save** to complete adding the action.

### Archive Incident-Specific Slack Channel This action automatically archives the dedicated Slack channel for the incident. To archive an incident-specific Slack channel, 1. Click on the **Slack logo** under Select to add action -> In the side panel, click on **Archive Incident-Specific Slack Channel**. 2. You'll have successfully added the new action.

### Send a Message to a Specific Slack Channel This action automatically sends a message to a specific Slack channel. To send a message to a Slack channel, 1. Click on the **Slack logo** under Select to add action -> In the side panel, click on **Send a Message to Specific Slack Channel.** 2. You can either input the Channel ID or select from the options in the drop-down. You can select only one channel. 3. Enter the **message** you would like to be automatically sent -> Click **Save**. 4. You'll have successfully added the new action.

{% hint style="warning" %} **Important****:** Kindly note that the bot needs to be manually added to the respective channel in Slack for seamless integration. {% endhint %} ### Send a Direct Message to a Slack User This action automatically sends a direct message to a specific Slack user. To send a message to a Slack user, 1. Click on the **Slack logo** under Select to add action -> In the side panel, click on **Send a Direct message to User.** 2. Select the user from the options in the drop-down. -> Enter the **message** you would like to be automatically sent. 3. Click **Save.** You'll have successfully added the new action.

{% hint style="warning" %} **Important**: In the context of API/Terraform configuration for the SendMessageToUser action, please specify the MemberID for referencing Slack users. **Steps to Obtain MemberID:** 1. In Slack, click on your profile icon in the bottom left. 2. Select "Profile." 3. Click on the hamburger icon below your name. 4. Copy the MemberID. {% endhint %} ## Jira Actions ### Create a Jira Ticket This action automatically creates a Jira ticket in Jira Cloud. To create a ticket in Jira Cloud, 1. Click on the **Jira logo** under Select to add action -> In the side panel, click on **Create a Jira Ticket.** 2. Select the **Jira Account**, **Jira Project**, and **Issue Type** from the options in the drop-down -> Enter the **ticket title** and **message** you would like to be automatically sent. 3. Click **Save.** You'll have successfully added the new action. This option supports templating variables, for the ones shown below: ``` incident_id incident_status incident_message incident_description service_id service_name alert_source_type alert_source_short_name payload ``` It will be utilized as such: Message: `{{event.incident_message}}`

## MS Teams Actions ### Send a message to a Microsoft Teams Channel This action automatically sends a direct message to a specific Microsoft Teams channel. To send a message on Microsoft Teams, 1. Click on the **Microsoft Teams logo** under Select to add action -> In the side panel, click on **Send a message to a specific Microsoft Teams Channel.** 2. Select the **channel** from the options in the drop-down -> Enter the **message** you would like to be automatically sent. 3. Click **Save.** You'll have successfully added the new action. This option supports templating variables, for the ones shown below: ``` incident_id incident_status incident_message incident_description service_id service_name alert_source_type alert_source_short_name payload ``` It will be utilized as such: Message: `{{event.incident_message}}` ### Send a message to specific Microsoft Teams User This action automatically sends a direct message to a specific Microsoft Teams user. To send a message on Microsoft Teams, 1. Click on the **Microsoft Teams logo** under Select to add action -> In the side panel, click on **Send a message to a specific Microsoft Teams User.** 2. Select the **user name** from the options in the drop-down -> Enter the **message** you would like to be automatically sent. 3. Click **Save.** You'll have successfully added the new action. This option supports templating variables, for the ones shown below: ``` incident_id incident_status incident_message incident_description service_id service_name alert_source_type alert_source_short_name payload ``` It will be utilized as such: Message: `{{event.incident_message}}` \\ *Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*