---
title: "Automated actions"
canonical: "https://support.appfire.com/space/CR/138085102/Automated%20actions"
format: markdown
---
> Macro (aura-html)
Each template can include an individually triggered sequence of actions that can be used in situations where you want to automate repetitive or routine tasks and enforce a consistent process for handling work items.
## How to add automated actions
You can add actions while creating or editing a template. Automated actions can work without adding comments; if you want to, you can only use an automated action. Actions are run in sequential order, one after another, and you can change their order by dragging and dropping them. You have three options:
#### 1) Set work item field
Using this, you can add or update a value in the Jira system and custom fields automatically through the Canned Responses templates. The most popular supported fields include:
- Labels
- Components
- Priority
- Text Fields (single line)
- User Pickers (single and multi)
- Resolution Field
- Select List (single and multiple choice)
- Radio Button
The fields must be available on a screen associated with Create or Edit work item operations.
> ℹ️ Please keep in mind that we are sometimes unable to retrieve values for Single- and Multi-Select custom field types. The following are some of the possible causes:
> ℹ️
> ℹ️ - The field doesn’t have configured options. Make sure you verify the field configuration [in the Jira settings](https://support.atlassian.com/jira-cloud-administration/docs/edit-a-custom-fields-options/).
> ℹ️ - The custom field is not [associated with any Create or Edit Work Item](https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/#Associating-a-screen-with-an-issue-operation) screen in your Jira. We’re unable to update fields that are presented only on the* Transition* or *Work Item View* screens and cannot be edited from a regular work item view.
#### 2) Transition to
Using this, you can transition the work item from one status to another. In addition to status, you can set a value for the Resolution field if needed.
#### **3) Send Slack notification**
This action lets you send automated notifications to specific Slack channels or users. For more detailed information on setting up this integration, please refer to the [documentation](https://appfire.atlassian.net/wiki/spaces/CR/pages/1554449107).
#### 4) Trigger a web request
- **To external service**
- **To trigger Jira Automation –** The ability to trigger Jira Automation is flexible – you can basically do all the things that you can do with automation, including changing a specific work item (edit/append summary or description of the request, add comments, etc.), and changing, adding,** **etc. any other work items.
## To trigger Jira automation from a template
**I. In Jira, ****[create an automation rule](https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/)**** in Jira Automation.**
1. Set its trigger to be **[Incoming webhook](https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#Automationtriggers-Incomingwebhook)**.
2. Copy the Webhook URL.
3. Finish the automation configuration.
**II. Create a new template**
1. Add the **Send web request** action.
2. Select the **POST** method from the dropdown and the URL copied from Jira Automation. The *Secret* box appears.
3. Copy and paste the Secret of the incoming webhook you created in Step I.
4. Fill out the Headers section.
5. Select the request mode. Set this option according to how your server is configured.
6. Add optional parameters** **to the body of the request, for example, by using [dynamic variables](https://appfire.atlassian.net/wiki/spaces/CR/pages/131534244/Create+a+template#response).
## Using templates with automated actions
When you insert a template with automated actions, they are scheduled to take place after the content (comment or work item description) is saved. If necessary, you can remove selected actions by clicking the trash icon next to them before saving and running actions. This will prevent them from running at that particular moment.
There is a sequence of execution for automated actions. If you utilize more than one template with actions while creating content, all of the actions will be queued and eventually run.
If an error occurs, the execution will be paused, and the following actions will not be executed until it is resumed. For example, if you have three automated actions and the first one fails, the following ones will be suspended and won’t be executed. To continue with the action, you’ll either need to click **Resume**, fix the work item for the first one, or delete the first one.
## Use cases
To suit your specific workflow and use case, you can mix and match and add multiple actions to the sequence for each template. You can check out some examples below.
#### Closing tickets
For thanking the customer and closing work items.
#### Reacting to known bugs
When the problem is known, agreed to be assigned to a particular person, labeled, and its status set to *In Progress*.
#### Creating new bug with Jira Automation
You can't use Canned Responses in Jira Automation since Jira doesn't provide the necessary APIs for this to be feasible. Instead, you can set up Jira automation rules and link them to CR, as described above.
Let’s look at an example to demonstrate how you can pass custom data via an automation webhook. For example, if you were to put this in the body:
`{`
` "data": {`
` "issueSummary": "$issueSummary$",`
` "originalTicket": "$issueKey$"`
` }`
`}`
This data could then be used in Jira automation fields: “Original ticket: {{webhookdata.originalTicket}}”.
#### Integrating with smart devices in the office
####
Sending notifications to Slack
---
> ℹ️ **Decide what comes next!** If there is anything you'd like to do with actions but currently can't, please let us know at the [Appfire Support Portal](https://apps.appf.re/crt/support) so we can prioritize accordingly.