---
schema_version: "1"
id: e00931540178295ab007fe0908ceee838855a431e14ad5190c1b9d62ef63cce0
title: Jira 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.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_flow_ref_third_party_jira.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 04195c62daa8141ff7f00e70a94a02ba9cf98394d60a15aa52438c5130537179
description: Connect to an external Jira account. Perform tasks like creating issues or updating comments. Use Jira as a data source (trigger) or a data target (action).
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Jira Connector

Connect to an external Jira account. Perform tasks like creating issues or updating comments. Use Jira 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.

## Connections

Connect to a source or target system by using its standard connection or an existing external named credential. 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 Basic authentication.

Basic authentication enables the user to provide a username and password when logging in to an external system.

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="d50845e111">FIELD</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d50845e114">DESCRIPTION</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="FIELD" class="slds-cell-wrap" style="vertical-align:top;" headers="d50845e111 ">Connection Name</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d50845e114 ">
              <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="d50845e111 ">Username</td>

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d50845e114 ">
              <p style="margin-bottom:0;">Enter the username to use to authenticate the requests.</p>
            </td>

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

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d50845e114 ">
              <p style="margin-bottom:0;">Enter the password to use to authenticate the requests.</p>
            </td>

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

            <td data-label="DESCRIPTION" class="slds-cell-wrap" style="vertical-align:top;" headers="d50845e114 ">
              <p style="margin-bottom:0;">Enter the URL of your instance.</p>
            </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 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 With Filter
- On New/UpdatedIssueTrigger

## 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 actions are available in Flow Builder.

- Add Comment
- Create Issue
- Create Issue Link
- Create Project
- Get Comments
- Get Issues
- Update Comment
- Update Issue
- Update Project
- Upsert Comment
- Upsert Issue

## Get Issues Action

The MuleSoft for Flow: Integration Get Issues action enables users to query searchable objects from each connector by using custom filter logic, providing an experience similar to Salesforce Flow's [Get Records element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_data_get.htm&release=264.0.0&type=5 "The Get Records element finds all Salesforce or Marketing Object records that meet the filter and sort conditions and stores values from the retrieved records in variables. You can retrieve Salesforce standard and custom object records, or Marketing Object records, by using the Get Records element.").

The MuleSoft for Flow: Integration Get Issues action:

- Defines the type of queried object, ensuring flexibility and adaptability to different data sources.
- Specifies available operators and enables the selection of fields, addition of conditions, and sorting of results.
- Defines the available types of logical operators.
- Includes extra metadata to describe the operators available for each field if the available operators differ based on the object type.
- Runs the actual query request and processes the response, ensuring accurately returned and properly formatted data.

## 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.

Jira 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.").