Provides integration with Atlassian Jira Cloud using OAuth and the REST API.
0.0.0.11 - Current release.
Use a Jira OAuth Connection for all methods.
| Property |
Type |
Description |
Cloud ID |
String |
Jira Cloud tenant ID. Run the Connection test to populate it automatically when the Atlassian account has access to one site, or to list available IDs when it has access to multiple sites. |
Client ID |
String |
Client ID from your Atlassian OAuth app. |
Client Secret |
Masked |
Client secret from your Atlassian OAuth app. |
Access Token |
Masked |
OAuth access token populated after you connect the account. |
Refresh Token |
Masked |
OAuth refresh token used to renew the access token when it expires. |
Scope |
String |
Space-delimited Atlassian scopes requested during authorization. The default value is read:jira-work offline_access. |
Timeout (seconds) |
Integer |
Timeout applied to Jira API calls. The default value is 30. |
- Create an Atlassian OAuth 2.0 app for Jira Cloud and use its
Client ID and Client Secret in the Connection.
- Authorize the
Connection so Flowgear can store Access Token and Refresh Token.
- Run the
Connection test to validate access and populate Cloud ID when only one Jira site is available. If multiple sites are returned, select the correct Cloud ID from the list shown by the test result.
- The default
Scope value is read:jira-work offline_access. Change it if the Jira operations you want to run need additional Atlassian scopes.
- This Node is for Jira Cloud. Jira Server and Jira Data Center are not supported.
The Jira Node exposes four invoke methods that use template-selected OperationId values from the embedded Jira OpenAPI schema.
Executes a Jira query operation and streams all result pages.
| Parameter |
Type |
Description |
Connection |
Connection |
The Jira OAuth Connection. |
OperationId |
String |
Identifier of the Jira operation to execute. Templates set this value for the selected operation. |
Parameters |
Object |
Optional route and query parameters required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
One response row per returned Jira item. Successful results expose Jira fields at the row root. When Jira responds with value, values, or issues, the Node emits each contained item separately. |
Executes a Jira create operation and sends request body items to the selected endpoint.
| Parameter |
Type |
Description |
Connection |
Connection |
The Jira OAuth Connection. |
OperationId |
String |
Identifier of the Jira operation to execute. Templates set this value for the selected operation. |
Parameters |
Object |
Optional route and query parameters required by the selected operation. |
Items |
Array |
Request body items for the selected create operation. One item sends one JSON object body. When the target operation supports array request bodies, multiple items are sent as one JSON array. |
| Return |
Type |
Description |
Response |
Array |
One response row per Jira response item. Successful rows include returned Jira fields and can include input so you can match the response to the submitted item. |
Executes a Jira update operation and sends request body items to the selected endpoint.
| Parameter |
Type |
Description |
Connection |
Connection |
The Jira OAuth Connection. |
OperationId |
String |
Identifier of the Jira operation to execute. Templates set this value for the selected operation. |
Parameters |
Object |
Optional route and query parameters required by the selected operation. |
Items |
Array |
Request body items for the selected update operation. One item sends one JSON object body. When the target operation supports array request bodies, multiple items are sent as one JSON array. |
| Return |
Type |
Description |
Response |
Array |
One response row per Jira response item. Successful rows include returned Jira fields and can include input so you can match the response to the submitted item. |
Executes a Jira delete operation.
| Parameter |
Type |
Description |
Connection |
Connection |
The Jira OAuth Connection. |
OperationId |
String |
Identifier of the Jira operation to execute. Templates set this value for the selected operation. |
Parameters |
Object |
Optional route and query parameters required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
One response row for the delete result. Successful rows include any Jira response fields returned by the endpoint. |
- Use templates to pick supported Jira operations. The built-in
Get Available Cloud IDs query template can help you discover Jira sites that the current OAuth account can access.
Query pages through Jira results internally. If you do not supply maxResults or maxResult, the Node requests up to 100 results per page.- Successful
Query rows do not add Flowgear success metadata, so downstream Steps receive the Jira payload fields directly.
Create, Update, and Delete add the standard Flowgear response fields status, statusMessage, and errorMessage to successful rows, and normalize provider failures into one error row.- When
Create or Update sends individual Items, the response can include an input field so you can match each result to the submitted payload.
- Query template return schemas are generated from the upstream OpenAPI sampler, so some templates can describe Jira's envelope shape more broadly than the flattened runtime output.