Appearance
Jira
Track issues, manage sprints, and organize projects with Jira.
| Detail | Value |
|---|---|
| Category | Project Management |
| Base URL | https://{domain}.atlassian.net |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | jira |
Using Jira in a workflow
- Go to Connections and click New Connection.
- Pick Jira from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown. The full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /search | Search issues using JQL |
POST /issue | Create an issue |
GET /issue/{issueIdOrKey} | Get an issue |
PUT /issue/{issueIdOrKey} | Update an issue |
POST /issue/{issueIdOrKey}/transitions | Transition an issue status |
GET /project | List all projects |
POST /issue/{issueIdOrKey}/comment | Add a comment to an issue |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /search
Search issues using JQL
| Detail | Value |
|---|---|
| Operation ID | pm.searchIssues |
| Method | GET |
| Path | /search |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
jql | query | string | Yes |
maxResults | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.searchIssues. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
POST /issue
Create an issue
| Detail | Value |
|---|---|
| Operation ID | pm.createIssue |
| Method | POST |
| Path | /issue |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
fields | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.createIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
GET /issue/{issueIdOrKey}
Get an issue
| Detail | Value |
|---|---|
| Operation ID | pm.getIssue |
| Method | GET |
| Path | /issue/{issueIdOrKey} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
issueIdOrKey | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.getIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
PUT /issue/{issueIdOrKey}
Update an issue
| Detail | Value |
|---|---|
| Operation ID | pm.updateIssue |
| Method | PUT |
| Path | /issue/{issueIdOrKey} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
issueIdOrKey | path | string | Yes |
Request Body
| Field | Type |
|---|---|
fields | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.updateIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
POST /issue/{issueIdOrKey}/transitions
Transition an issue status
| Detail | Value |
|---|---|
| Operation ID | pm.transitionIssue |
| Method | POST |
| Path | /issue/{issueIdOrKey}/transitions |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
issueIdOrKey | path | string | Yes |
Request Body
| Field | Type |
|---|---|
transition | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.transitionIssue. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
GET /project
List all projects
| Detail | Value |
|---|---|
| Operation ID | pm.listProjects |
| Method | GET |
| Path | /project |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.
POST /issue/{issueIdOrKey}/comment
Add a comment to an issue
| Detail | Value |
|---|---|
| Operation ID | pm.addComment |
| Method | POST |
| Path | /issue/{issueIdOrKey}/comment |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
issueIdOrKey | path | string | Yes |
Request Body
| Field | Type |
|---|---|
body | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Jira connection from the Connection dropdown.
- In the Operation dropdown, select
pm.addComment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked: fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Jira API reference.