--- title: "Automate Jira actions with Salesforce Flow Builder" canonical: "https://support.appfire.com/space/CSFJIRA/3627581468/Automate%20Jira%20actions%20with%20Salesforce%20Flow%20Builder" format: markdown --- > Macro (aura-html) ## Before you start Make sure you: - Have a working connection to your Jira instance (set up by your Salesforce administrator). - Have an account with permission to create work items in the target Jira space. - Map the entities for the Salesforce object type and Jira work item type you want to create. See [Configure entity, field and value mappings](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1854180614). - Have enabled** Automatic Pull** in the general configuration of the connection you'll select in the flow. - The specific association between the Salesforce record and the Jira work item has **Auto-Pull** turned on. Associations set to View-only are not updated by this action. - Understand the Flows in Salesforce. See [Build Record-Triggered Flows Guide](https://trailhead.salesforce.com/content/learn/modules/record-triggered-flows/build-a-record-triggered-flow). ## Set up the flow 1. In Salesforce, open the **Setup** menu. 2. Search for **Flows** in the **Quick Find **box, and click **New Flow** to open the Flow Builder. 3. In the *New Automation *window, select **Record-Triggered Flow**. To use **Push updates to Jira** in a schedule-triggered flow, select **Schedule-Triggered Flow** instead. See [Use Push updates to Jira in a schedule-triggered flow](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/3627581468/Automate+Jira+actions+with+Salesforce+Flow+Builder#Use-Push-updates-to-Jira-in-other-flow-types) for the differences. 4. Under *Configure Start,*** **select the Salesforce object type whose records you want to trigger the flow (for example, Case). 5. Select the event that will trigger the flow. For example, **A record is created**. - **A record is created ** - **A record is updated ** - **A record is created or updated** - **A record is deleted** 6. Click the **Add element **() icon, then select **Action**. 7. Select the Connector action you want to use: 1. **Create Jira work item** Creates a new Jira work item from the Salesforce record and automatically associates it with the record. 2. **Push updates to Jira** Pushes changes from the Salesforce record to Jira work items that are already associated with it. The update is sent through the connection you select and follows the synchronization rules configured for that connection. The connection must have** Allow Automatic Pull **enabled, and the association must have **Auto-Pull** on. 8. Type the **Label **name for the element, for example, `Bug flow`. The **API name** field fills out automatically. 9. Fill in the fields for the selected action - **Record ID **-** **The Salesforce record the work item should use. In most cases, this is the record that triggered the flow; click **Use Triggering Record** to fill it in automatically. However, it can also reference a different, specific record depending on your use case. Set Record ID instead of the triggering record. - **Object API name - **The type of Salesforce object the record belongs to (for example, Case or Opportunity). Select it from the dropdown list. You can start typing to filter it. - **Select a connection **-** **The Jira connection you want to use for the automation. If you selected **Create Jira work item**, also configure: - **Jira space **-** **The Jira space the new work item should be created in. - **Work item type** - The type of work item you want to create automatically (for example, bug, task, or story). Make sure that you have mapped the entities for the selected work item type in Jira. In this example, you need a mapping for the Bug Jira work item type and a Case object type. To learn more, see [Configure entity, field and value mappings](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1854180614). If you selected **Push updates to Jira**, you don't need a Jira space or work item type. The connector pushes record changes to applicable Jira work items already associated with the Salesforce record on the selected connection. 10. Type the **Flow Label name**, for example, `Create a Jira bug on a Case` or `Push Case updates to Jira`. The Flow API name fills out automatically. ![Flow settings showing the Flow Label field and automatically generated Flow API name.](media://e005ff2c-b04d-4ac7-b7f3-08ae59f9c210) 11. Click **Activate**. When the flow runs: - **Create Jira work item** creates a new Jira work item and associates it with the Salesforce record. - **Push updates to Jira** synchronizes the Salesforce record with its applicable existing Jira associations on the selected connection, according to the connection's synchronization rules. ### Example: Escalate a case to Jira **Scenario:** Your support team wants every Salesforce case marked "Escalated" to automatically become a Bug in the Engineering Jira project. - **Trigger:** Record-Triggered Flow on `Case`, when `Status` changes to `Escalated`. - **Record:** The Case record. - **Object API name:** `Case` - **Connection name:** `Engineering Jira` - **Jira space:** `ENG` - **Jira work item type:** `Bug` **Result:** As soon as a Case is escalated, a Bug appears in the ENG space, associated to the Case. Each Create Jira work item step works with one object type per group of records. If your Flow handles multiple object types, add a decision step to route records or run the action per object type. ## **Use Push updates to Jira in schedule-triggered flow** You can also use Push updates to Jira in a schedule-triggered flow, for example, to push updates for a specific record at regular intervals. The same prerequisites apply: Allow Automatic Pull on the connection and Auto-Pull on the association. In that case, you must provide these values: - **Record ID** – the ID of a specific Salesforce record. - **Object API name** – the object the record belongs to, for example, Case. - **Select a connection **-** **The Jira connection you want to use for the automation. When the flow runs with valid values, the action enqueues the push. The sync changes can take a moment to appear in Jira. ## Need help? Contact your Salesforce administrator if: - The connection you need isn't in the list. - You don't see the Jira space or work item type you expect (this usually means a permissions problem in Jira). ## Learn more - [Build Record-Triggered Flows Guide](https://trailhead.salesforce.com/content/learn/modules/record-triggered-flows/build-a-record-triggered-flow)