---
schema_version: "1"
id: 1ce3d92a48b5ee20811618e196dbf79847974deed7cce42e89f90d61e6e86111
title: Jira OAuth (Authorization Code Flow) Connector
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_flow_ref_third_party_jira_oauth.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_ref_third_party_jira_oauth.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 82d78ca5b76735cc847eedb05d6f3f0a8b81183d306c86dc1a1a54b213490e83
description: Connect to an external Jira account that uses an Authorization Code Flow connection. Perform tasks like creating issues or updating comments. Use Jira OAuth as a data source (trigger) or a data target (action).
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Jira OAuth (Authorization Code Flow) Connector

Connect to an external Jira account that uses an Authorization Code Flow connection. Perform tasks like creating issues or updating comments. Use Jira OAuth as a data source (trigger) or a data target (action).

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">This feature requires the MuleSoft for Flow: Integration add-on. Exceptions are segment-triggered flows, activation-triggered flows, and broadcast flows, which don't require the MuleSoft for Flow: Integration add-on. <strong>Professional</strong> Edition requires the API access add-on. To purchase an add-on, contact your Salesforce account executive.</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive.</td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note You can edit or delete connections only in the Automation app.

## Prerequisites

To connect successfully and use all features, such as the Test Connection action, configure these Classic Scopes in your Jira OAuth 2.0 settings.

read:jira-user

The connector can read user data.

read:jira-work

The connector can read issue and project data.

write:jira-work

Required to create or update issues and comments.

manage:jira-project

Required for project-level management tasks.

manage:jira-configuration

Required to manage system configurations.

For more information, see the Atlassian Cloud Scopes documentation.

## Connections

To connect to a system, whether it’s a data source or a data target, create a connection with that system’s required credentials. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the [Integrations tab](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections.htm&release=264.0.0&type=5 "The Integrations tab includes a list of all the connections for your org.") or in Flow Builder.

**Standard Connection**

This system uses Authorization Code Flow (OAuth2BrowserFlow) authentication.

Authorization Code Flow authentication includes features that extend OAuth 2.0 protocol functionality and security.

This system requires this credential information for its [connections](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections_create_connection.htm&release=264.0.0&type=5).

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d108090e163">FIELD</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d108090e166">DESCRIPTION</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e163 ">Connection Name</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e166 ">
              <p dir="ltr">Enter a unique connection name that helps you remember the details of this
                connection. Salesforce hides the credentials after you create the connection. Reuse
                connections as needed.</p>
              <p style="margin-bottom:0;" dir="ltr">Anyone with the Manage Integration Connections permission can see and use all
                connections in the org.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e163 ">URL</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e166 ">
              <p>Enter the instance URL:
                <samp class="filepath">https://api.atlassian.com/ex/jira/<var>cloudid</var></samp>.
              </p>
              <p style="margin-bottom:0;">To find your Cloud ID, go to
                <samp class="filepath">https://<var>your_domain</var>.atlassian.net/_edge/tenant_info</samp>
                and copy the <code>CloudID</code> value. For example:
                <code>11223344-a1b2-3b33-c444-def123456789</code>.
              </p>
            </td>

          </tr>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e163 ">Environment</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d108090e166 ">Select the environment type for the connection.</td>

          </tr>
        </tbody>
      </table>

**Named Credential Connection**

Select a pre-existing named credential from Setup to use for your external system connections.

Before connecting to your external system with a named credential, first create or use an existing authenticated [named credential and external credential that is enabled for your users.](https://help.salesforce.com/s/articleView?id=xcloud.nc_named_creds_and_ext_creds.htm&type=5&language=en_US)

To ensure a successful [connection](https://help.salesforce.com/s/articleView?id=platform.automate_ala_connections_create_connection.htm&release=264.0.0&type=5 "Select a named credential from Setup to use for your external system connections.") for use in a flow, use only one principal for each named credential.

- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

When you create a connection with an existing named credential, note these behaviors:

- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.

## Triggers

A trigger initiates the flow when a specified event occurs. Triggers are important for automating business processes because they react to real-time data changes in various systems. For more information about triggers, refer to [Create a Flow with a Connector as a Trigger](https://help.salesforce.com/s/articleView?id=platform.automate_build_flow_esct_third_party_as_trigger.htm&release=264.0.0&type=5 "To trigger a flow when a change happens in a third-party system, use an External System Change-Triggered flow. A poller checks for new records on a schedule and creates flow interviews when records are found. Create the flow from scratch or from a template.").

These Jira OAuth triggers are available in Flow Builder.

- On New Comment Trigger
- On New Issue Trigger
- On New Issue Trigger With Filter
- On New or Updated Issue Trigger
- On New Or Updated Issue Trigger With Filter

## Actions

An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to [Create a Flow with a Connector as an Action](https://help.salesforce.com/s/articleView?id=platform.automate_build_flow_esct_third_party_as_action.htm&release=264.0.0&type=5 "To integrate your flow with an external system, add MuleSoft for Flow: Integration connectors as actions to all existing flow types. You can add connectors to flows that trigger external system changes, records, schedules, Data Cloud-triggered flows, or autolaunched flows.").

These Jira OAuth actions are available in Flow Builder.

- Add Attachment
- Add User To Group
- Add Watcher
- Create Comment
- Create Group
- Create Issue
- Create Issue Link
- Create Project
- Delete Watcher
- Get Attachment Content
- Get Comments
- Get Issues
- Remove Group
- Remove User From Group
- Update Comment
- Update Issue
- Update Project
- Upsert Comment
- Upsert Issue

## File Actions

With MuleSoft for Flow integration file actions, your flows can transfer, upload, and return external files up to 15 MB. The actions provide a file as a reusable object variable for subsequent flow actions, such as sending a file to an external system.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

Connector-driven file operations create files. Delete files after they’re no longer needed. Delete files after flow use by adding a Delete element to the flow, or manually delete files from the Files tab.

The Jira OAuth connector supports these file-based actions:

- Attach File to Jira Issue
- Get File from Jira

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png)

Tip For more information about the API, see the external system's API documentation.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_important.png)

Important

For information about specific limitations for connections and third-party connectors, see [MuleSoft for Flow: Integration Limits & Considerations](https://help.salesforce.com/s/articleView?id=platform.automate_flow_considerations_mulesoft_for_flow_limits.htm&release=264.0.0&type=5 "When establishing connections to external systems, keep these limitations in mind.").