⚙Tool
Jira Service Management Tools
List service desks and create, retrieve, and list customer requests in Jira Service Management
Manage IT service desks and customer requests through the Jira Service Management REST API. Use these tools in a workflow to discover service desks, raise new customer requests, fetch a single request, and list existing requests — for example, to triage support tickets or open requests automatically from another system.
Overview
| Property | Value |
|---|---|
| Provider | jira-service-management |
| Category | tools |
| Auth | Basic Auth (Atlassian email + API token, sent as a base64-encoded Authorization: Basic header) |
Operations
| Operation | Tool ID | Description |
|---|---|---|
| List Service Desks | jira_service_management_list_servicedesks | List the service desks available in Jira Service Management |
| Create Request | jira_service_management_create_request | Create a new customer request in a Jira Service Management service desk |
| Get Request | jira_service_management_get_request | Retrieve a single customer request by issue ID or key |
| List Requests | jira_service_management_list_requests | List customer requests, optionally scoped to a service desk |
Configuration
jira_service_management_list_servicedesks
List the service desks available in Jira Service Management.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Atlassian site URL (e.g. https://your-domain.atlassian.net) |
email | string | Yes | Atlassian account email |
apiToken | string | Yes | Atlassian API token. Secret — treat as a credential and supply via an environment variable. |
limit | number | No | Maximum number of service desks to return |
jira_service_management_create_request
Create a new customer request in a Jira Service Management service desk.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Atlassian site URL (e.g. https://your-domain.atlassian.net) |
email | string | Yes | Atlassian account email |
apiToken | string | Yes | Atlassian API token. Secret — treat as a credential and supply via an environment variable. |
serviceDeskId | string | Yes | ID of the service desk to create the request in |
requestTypeId | string | Yes | ID of the request type |
requestFieldValues | json | Yes | Field values for the request as a JSON object (e.g. {"summary":"...","description":"..."}) |
jira_service_management_get_request
Retrieve a single customer request by issue ID or key.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Atlassian site URL (e.g. https://your-domain.atlassian.net) |
email | string | Yes | Atlassian account email |
apiToken | string | Yes | Atlassian API token. Secret — treat as a credential and supply via an environment variable. |
issueIdOrKey | string | Yes | Issue ID or key of the request (e.g. SD-123) |
jira_service_management_list_requests
List customer requests, optionally scoped to a service desk.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteUrl | string | Yes | Atlassian site URL (e.g. https://your-domain.atlassian.net) |
email | string | Yes | Atlassian account email |
apiToken | string | Yes | Atlassian API token. Secret — treat as a credential and supply via an environment variable. |
serviceDeskId | string | No | Filter requests by service desk ID |
limit | number | No | Maximum number of requests to return |
Outputs
jira_service_management_list_servicedesks
data(json) — Array of service desk objectsmetadata(json) — List metadata, with properties:count(number) — Number of service desks returnedisLastPage(boolean) — Whether this is the last page
jira_service_management_create_request
data(json) — The created customer request objectmetadata(json) — Request identifiers, with properties:id(string) — Issue IDissueKey(string) — Issue key
jira_service_management_get_request
data(json) — The requested customer request objectmetadata(json) — Request identifiers, with properties:id(string) — Issue IDissueKey(string) — Issue key
jira_service_management_list_requests
data(json) — Array of customer request objectsmetadata(json) — List metadata, with properties:count(number) — Number of requests returnedisLastPage(boolean) — Whether this is the last page
YAML Example
jira_service_management_1:
type: jira_service_management
name: "Jira Service Management"
inputs:
operation: "jira_service_management_create_request"
siteUrl: "https://your-domain.atlassian.net"
email: "you@example.com"
apiToken: "{{JIRA_SERVICE_MANAGEMENT_API_TOKEN}}"
serviceDeskId: "1"
requestTypeId: "25"
requestFieldValues: '{"summary": "Need help", "description": "Details here"}'
connections:
outgoing:
- target: next-block-idTips
- Authentication is Basic Auth: provide your Atlassian account
emailand anapiTokenyou generate at id.atlassian.com (Security → API tokens). The tool combinesemail:apiTokenand base64-encodes it into theAuthorization: Basicheader — never the password to your Atlassian login. Keep the token in an environment variable like{{JIRA_SERVICE_MANAGEMENT_API_TOKEN}}. - Run
jira_service_management_list_servicedesksfirst to discover aserviceDeskId, then use that ID (plus arequestTypeId) when callingjira_service_management_create_request. You can reference the discovered value downstream with{{jira_service_management_1.data}}. requestFieldValuesmust be a JSON object — at minimum it usually needssummaryanddescription. The exact fields depend on the request type configured in your service desk.siteUrlis trimmed and any trailing slash is removed automatically, so bothhttps://your-domain.atlassian.netandhttps://your-domain.atlassian.net/work.