You are here:
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
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Connections
To connect to a system, whether it's a data source or a data target, create a connection with that system's standard connection or with 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 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.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | 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. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| Username | Enter the username to use to authenticate the requests. |
| Password | Enter the password to use to authenticate the requests. |
| URL | Enter the URL of your instance. |
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.
To ensure a successful connection 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.
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.
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.
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.
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
MuleSoft for Flow: Integration file actions support binary file transfers up to 15 MB, enabling your flow to upload and return files, such as email attachments or documents, from an external system. The actions provide a file as a reusable object variable for subsequent flow actions, such as sending a file to an external system.
Jira Connector supports these file-based actions:
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
