We aim to provide accurate and helpful details about third‑party tools, but we can't guarantee that this information is always complete or up to date. If you notice any discrepancies, feel free to share them in the feedback section below. For the most reliable information, please always refer to the third‑party tool's official documentation.
Jira Service Management is an IT service management (ITSM) platform from Atlassian for managing service requests, incidents, and changes.
This component allows managing service desks, requests, request types, queues, approvals, organizations, and customers within Jira Service Management.
API documentation
This component was built using the Jira Service Management Cloud REST API.
Connections
Basic Authentication
Authenticate using an email address and API token.
To authenticate with Jira Service Management using Basic Authentication, an email address and an API token are required.
Prerequisites
- A Jira Cloud instance with Jira Service Management enabled
- An Atlassian account with appropriate permissions
Setup steps
- Navigate to Atlassian Account API Tokens
- Select Create API token
- Enter a label for the token and select Create
- Copy the generated API token value
For more information on generating API tokens, refer to the Atlassian documentation.
Configure the connection
Create a connection of type Basic Authentication and configure the following fields:
- For Username, enter the email address associated with the Atlassian account
- For API Key, enter the API token generated in the previous step
- For Host, enter the Atlassian site hostname without
https://(e.g.,example-company.atlassian.net)
| Input | Comments | Default |
|---|---|---|
| Username | The Atlassian account email address used for authentication. | |
| API Key | The Atlassian API token. Generate one at Atlassian API Tokens. | |
| Host | The Atlassian site hostname (without https://). |
OAuth 2.0
Authenticate using OAuth 2.0.
To connect to Jira Service Management using OAuth 2.0, create and configure an OAuth 2.0 (3LO) application in the Atlassian Developer Console.
Prerequisites
- An Atlassian account with access to Jira Service Management
- Access to the Atlassian Developer Console
Setup steps
- Navigate to the Atlassian Developer Console and select Create then OAuth 2.0 integration
- Enter a name for the application and select Create
- In the left sidebar, select Authorization and then select Add next to OAuth 2.0 (3LO)
- Enter the OAuth 2.0 callback URL as the Callback URL:
- EU:
https://oauth2.flowbuilder.eu.lansweeper.com/callback - US:
https://oauth2.flowbuilder.us.lansweeper.com/callback
- EU:
- Select Save changes
- In the left sidebar, select Permissions and configure the required scopes for Jira Service Management access
- In the left sidebar, select Settings to find the Client ID and Secret values
Refer to the Atlassian OAuth 2.0 (3LO) documentation for detailed setup instructions.
Configure the connection
Create a connection of type OAuth 2.0 and configure the following fields:
-
For Authorize URL, the default value is pre-configured for Atlassian Cloud APIs:
https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent -
For Token URL, the default value is:
https://auth.atlassian.com/oauth/token -
For Scopes, the default value includes common Jira Service Management scopes:
read:servicedesk-request write:servicedesk-request manage:servicedesk-customer read:jira-user offline_accessRefer to the Atlassian scopes documentation for additional scope information.
-
Enter the Client ID and Client Secret from the application settings in the Developer Console
-
Optionally, enter the Atlassian Site Name if the Atlassian account has access to multiple Jira sites (e.g.,
example-company.atlassian.net). If left blank, the connection uses the first accessible site.
This connection uses OAuth 2.0, a common authentication mechanism for integrations.
Read about how OAuth 2.0 works here.
| Input | Comments | Default |
|---|---|---|
| Authorize URL | The OAuth 2.0 Authorization URL for Atlassian. The audience parameter is required for cloud APIs. | https://auth.atlassian.com/authorize?audience=api.atlassian.com&prompt=consent |
| Token URL | The OAuth 2.0 Token URL for Atlassian. | https://auth.atlassian.com/oauth/token |
| Scopes | Space-delimited list of OAuth 2.0 scopes for Jira Service Management access. | read:servicedesk-request write:servicedesk-request manage:servicedesk-customer read:jira-user read:ops-alert:jira-service-management write:ops-alert:jira-service-management delete:ops-alert:jira-service-management read:ops-config:jira-service-management write:ops-config:jira-service-management delete:ops-config:jira-service-management read:cmdb-object:jira write:cmdb-object:jira delete:cmdb-object:jira read:cmdb-schema:jira write:cmdb-schema:jira delete:cmdb-schema:jira read:cmdb-type:jira write:cmdb-type:jira delete:cmdb-type:jira read:cmdb-attribute:jira offline_access |
| Client ID | OAuth 2.0 Client ID from the Atlassian Developer Console. | |
| Client Secret | OAuth 2.0 Client Secret from the Atlassian Developer Console. | |
| Atlassian Site Name | Optional Atlassian site name or URL to connect to. By default, connects to the first accessible site. Set this when the authenticated account has access to multiple Jira sites. |
Ops Integration API Key
Authenticate with the JSM Ops Integration Events API using a GenieKey integration API key.
| Input | Comments | Default |
|---|---|---|
| API Key | GenieKey API key generated from a JSM Ops API integration. Find this under Operations > Integrations in your JSM project. |
Triggers
New Ops alerts
Fetches new alerts created in Jira Service Management Ops on a recurring schedule.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Additional Query | Atlassian Ops query terms appended to the built-in createdAt filter. Uses OpsGenie query language syntax. |
New service requests
Fetches new service requests created in Jira Service Management on a recurring schedule.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | Limits new requests to a specific service desk. When omitted, requests from all accessible service desks are returned. |
Actions
Acknowledge Integration Alert
Acknowledges an alert via the integration API. Returns an asynchronous request ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The alert identifier — by default the alert ID. To use the tiny ID or alias, set Identifier Type accordingly. | |
| Identifier Type | Format of the alert identifier. Use alias only when the alert is in OPEN status — closed alerts cannot be referenced by alias. |
id |
| User | Display name of the user performing the action. Used to attribute the alert action in audit history. | |
| Source | Source of the alert. Defaults to the IP address of the request when omitted. | |
| Note | Additional note posted alongside the alert action. |
Acknowledge Ops alert
Acknowledges an Ops alert.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The identifier of the alert. |
Add Attachment
Attaches a previously uploaded temporary file to a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Temporary File ID | The ID of the temporary file previously uploaded via the Upload Attachment action. |
Add Comment
Adds a comment to a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Comment Body | The message to post on the request. Supports plain text and is rendered in the customer portal. | |
| Public | When true, the comment is visible to the customer. When false, the comment is internal only. | true |
Add customers to service desk
Adds one or more existing customers to the specified service desk by accountId.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Account IDs | The Atlassian accountIds to include in the request. Provide a JSON array of string identifiers. |
Add Integration Alert note
Adds a note to an alert via the integration API. Returns an asynchronous request ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The alert identifier — by default the alert ID. To use the tiny ID or alias, set Identifier Type accordingly. | |
| Identifier Type | Format of the alert identifier. Use alias only when the alert is in OPEN status — closed alerts cannot be referenced by alias. |
id |
| Note | The note content to add to the alert. | |
| User | Display name of the user performing the action. Used to attribute the alert action in audit history. | |
| Source | Source of the alert. Defaults to the IP address of the request when omitted. |
Add organization to service desk
Links an organization to the specified service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. |
Add users to organization
Adds users to an organization by accountId.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Account IDs | The Atlassian accountIds to include in the request. Provide a JSON array of string identifiers. |
Approve or decline request
Approves or declines a pending approval on a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Approval ID | The ID of the approval to respond to. Use the List Approvals action or the Approval data source to find this value. | |
| Decision | Whether to approve or decline the request. |
Close Integration alert
Closes (resolves) an alert via the integration API. Returns an asynchronous request ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The alert identifier — by default the alert ID. To use the tiny ID or alias, set Identifier Type accordingly. | |
| Identifier Type | Format of the alert identifier. Use alias only when the alert is in OPEN status — closed alerts cannot be referenced by alias. |
id |
| User | Display name of the user performing the action. Used to attribute the alert action in audit history. | |
| Source | Source of the alert. Defaults to the IP address of the request when omitted. | |
| Note | Additional note posted alongside the alert action. |
Close Ops alert
Closes (resolves) an Ops alert.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The identifier of the alert. |
Create Asset object
Creates a new Assets/CMDB object of the specified object type with the provided attributes.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Schema ID | ID of the Assets object schema. Use the Select Schema data source or List Schemas action. | |
| Object Type ID | ID of the object type. Use the Select Object Type data source after picking a schema. | |
| Attributes | JSON array of attribute payloads for this object. Each item has the shape { objectTypeAttributeId, objectAttributeValues: [{ value }] }. |
|
| Additional Fields | Extra request body properties to merge into the payload alongside the standard inputs. Provide a JSON object keyed by field name. |
Create customer
Creates a portal-only customer account, adds them to the specified service desk, and sends an invite email.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| The email address of the new portal-only customer. | ||
| Display Name | The full name shown for the customer in the portal and on issues they raise. |
Create Integration alert
Ingests a new alert into JSM Ops via the integration API. Returns an asynchronous request ID; use Get Integration Alert Request to check processing status.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Message | The alert message that summarises what happened. Truncated to 130 characters by Atlassian. | |
| Alias | Client-defined identifier for deduplication. Subsequent alerts with the same alias and OPEN status are de-duplicated to the first one. | |
| Description | Detailed message body. Markdown is supported. Truncated to 15,000 characters by Atlassian. | |
| Responders | JSON array of responder objects to assign. Each item must include type (team, user, escalation, schedule) and one of id, name, or username. |
|
| Visible To | JSON array restricting alert visibility to specific teams or users. Same shape as Responders. | |
| Actions | JSON array of custom action names that can later be invoked on the alert. | |
| Tags | JSON array of string tags to attach to the alert. | |
| Details | JSON object of arbitrary key/value pairs stored alongside the alert. | |
| Entity | Optional entity field used to specify which domain the alert is related to (e.g. a server name). | |
| Source | Source of the alert. Defaults to the IP address of the request when omitted. | |
| Priority | Priority level of the alert. Defaults to P3. | P3 |
| User | Display name of the user performing the action. Used to attribute the alert action in audit history. | |
| Note | Additional note posted alongside the alert action. |
Create Ops alert
Creates a new alert in JSM Ops. Returns an asynchronous request ID; use Get Ops Alert to fetch the resulting alert once processed.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Message | Brief alert summary. Truncated to 130 characters by Atlassian. | |
| Description | Detailed message body. Markdown is supported. Truncated to 15,000 characters by Atlassian. | |
| Priority | Priority level of the alert. Defaults to P3. | P3 |
| Alias | Client-defined identifier for deduplication. Subsequent alerts with the same alias and OPEN status are de-duplicated to the first one. | |
| Tags | JSON array of string tags to attach to the alert. | |
| Additional Fields | Extra request body properties to merge into the payload alongside the standard inputs. Provide a JSON object keyed by field name. |
Create organization
Creates a new organization.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization Name | A unique display label for the organization, shown to agents and customers in the portal. |
Create portal-only customer
Creates a portal-only customer account without linking them to a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| The email address of the new portal-only customer. | ||
| Display Name | The full name shown for the customer in the portal and on issues they raise. |
Create request
Creates a new service request in the specified service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Request Type ID | The ID of the request type to create the request as. Use the List Request Types action or the Request Type data source. | |
| Summary | A brief, one-line subject shown in the portal and issue list. | |
| Description | Additional detail about the request. Displayed on the request view for agents and customers. | |
| Field Values | JSON object of additional request field values required by the request type. Keys are field IDs. | |
| Raise On Behalf Of | The accountId of the customer to raise the request on behalf of. If omitted, the request is raised by the authenticated user. | |
| Additional Fields | Extra request body properties to merge into the payload alongside the standard inputs. Provide a JSON object keyed by field name. |
Delete Asset object
Deletes an Assets/CMDB object by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Object ID | Numeric ID of the Assets object (e.g. 425). Distinct from the human-readable object key (e.g. ITAM-425). |
Delete Ops alert
Deletes an Ops alert.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The identifier of the alert. |
Delete organization
Deletes an organization by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. |
Delete organization property
Removes a custom property from an organization by key.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Property Key | The key identifying the custom property to store against the organization. |
Get Asset object
Returns a single Assets/CMDB object by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Object ID | Numeric ID of the Assets object (e.g. 425). Distinct from the human-readable object key (e.g. ITAM-425). |
Get Asset schema
Returns a single Assets/CMDB object schema by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Schema ID | ID of the Assets object schema. Use the Select Schema data source or List Schemas action. |
Get Integration Alert request
Returns the processing status of an asynchronous Integration Events request by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Request ID | The async request ID returned by a previous Ops Integration Events action. |
Get Ops alert
Returns a single Ops alert by identifier.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The identifier of the alert. |
Get Ops on-call
Returns the recipients currently on-call for the specified Ops schedule.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Schedule | The ID of the schedule. | |
| Flatten On-Call | When true, returns only the user IDs of the on-call participants. When false, returns the full rotation tree. | false |
| Reference Date | ISO-8601 timestamp at which to evaluate the on-call list. Defaults to the current time. |
Get Ops schedule
Returns a single Ops schedule by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Schedule | The ID of the schedule. |
Get organization
Returns a single organization by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. |
Get organization property
Returns the value of a single organization property.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Property Key | The key identifying the custom property to store against the organization. |
Get request
Returns a single service request by issue ID or key.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. |
Get request type
Returns a single request type for a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Request Type ID | The ID of the request type to create the request as. Use the List Request Types action or the Request Type data source. |
Get service desk
Returns a single service desk by ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. |
List Approvals
Returns the approvals for a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List Asset schemas
Returns all Assets/CMDB object schemas in the workspace.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start At | Index of the first result to return. | 0 |
| Max Results | Maximum number of results per page. | 50 |
| Additional Query Parameters | Extra query string parameters to merge into the request URL alongside the standard inputs. Provide a JSON object keyed by parameter name. |
List Comments
Returns comments for a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List customers
Returns customers associated with a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List Ops alerts
Returns alerts in JSM Ops, optionally filtered by query.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Query | Atlassian Ops query string used to filter the alert list (e.g. status: open AND priority: P1). |
|
| Sort | Field to sort the alerts by (e.g. createdAt, priority). |
|
| Order | Sort order applied alongside the Sort field. | desc |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Offset | Index of the first result to return. | 0 |
| Size | Maximum number of results per page (Atlassian max: 100). | 20 |
| Additional Query Parameters | Extra query string parameters to merge into the request URL alongside the standard inputs. Provide a JSON object keyed by parameter name. |
List Ops schedules
Returns all on-call schedules configured in JSM Ops.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Query | Filters schedules by name (substring match). | |
| Offset | Index of the first result to return. | 0 |
| Size | Maximum number of results per page (Atlassian max: 50). | 25 |
| Additional Query Parameters | Extra query string parameters to merge into the request URL alongside the standard inputs. Provide a JSON object keyed by parameter name. |
List organization properties
Returns the property keys stored against an organization.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. |
List organizations
Returns all organizations in the Jira Service Management instance.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List organization users
Returns users associated with an organization.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List queue issues
Returns the issues in a service desk queue.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Queue ID | The unique identifier of the queue. Use the List Queues action or the Queue data source. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List queues
Returns queues for a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List requests
Returns service requests for the given service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List request types
Returns all request types for a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List schema object types
Returns all object types defined in the specified Assets/CMDB object schema.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Schema ID | ID of the Assets object schema. Use the Select Schema data source or List Schemas action. | |
| Additional Query Parameters | Extra query string parameters to merge into the request URL alongside the standard inputs. Provide a JSON object keyed by parameter name. |
List service desk organizations
Returns organizations linked to a service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List service desks
Returns all service desks in the Jira Service Management instance.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List SLA information
Returns SLA information for a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
List transitions
Returns available status transitions for a service request.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Fetch All | When true, automatically fetches all pages of results using pagination. Ignores start and limit when true. | false |
| Start | The starting index of the returned items. First item is 0. | 0 |
| Limit | The maximum number of items to return per page. |
Raw Request
Send raw HTTP request to the Jira Service Management REST API.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| URL | Input the path only (e.g., /servicedesk). The base URL is resolved from the connection automatically. | |
| Method | The HTTP method to use. | |
| Data | The HTTP body payload to send to the URL. | |
| Form Data | The Form Data to be sent as a multipart form upload. | |
| File Data | File Data to be sent as a multipart form upload. | |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Header | A list of headers to send with the request. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Timeout | The maximum time that a client will await a response to its request | |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Remove customers from service desk
Removes one or more customers from the specified service desk by accountId.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Account IDs | The Atlassian accountIds to include in the request. Provide a JSON array of string identifiers. |
Remove organization from service desk
Unlinks an organization from the specified service desk.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. |
Remove users from organization
Removes users from an organization by accountId.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Account IDs | The Atlassian accountIds to include in the request. Provide a JSON array of string identifiers. |
Revoke portal-only access
Revokes a user's portal-only access so they can no longer log in as a portal customer.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Account ID | The Atlassian accountId of the customer. |
Search Asset objects
Searches Assets/CMDB objects using AQL (Asset Query Language).
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| AQL Query | Asset Query Language expression used to filter objects (e.g. objectType = "Computer" AND Name LIKE "web-*"). |
|
| Include Attributes | When true, full attribute values are returned for each object. Disable to reduce payload size. | true |
| Start At | Index of the first result to return. | 0 |
| Max Results | Maximum number of results per page. | 50 |
Set organization property
Stores a custom JSON value against an organization under the specified property key.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Organization ID | The unique identifier of the organization. Use the List Organizations action or the Organization data source. | |
| Property Key | The key identifying the custom property to store against the organization. | |
| Property Value | JSON value to store for the property. Can be any valid JSON (object, array, string, number, or boolean). |
Snooze Ops alert
Snoozes an Ops alert until the supplied ISO-8601 timestamp.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Alert Identifier | The identifier of the alert. | |
| Snooze Until | ISO-8601 timestamp until which the alert is snoozed (e.g. 2026-05-04T18:30:00Z). |
Transition request
Transitions a service request to a new status.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Issue ID or Key | The ID or key of the service request issue (e.g., IT-42 or 10001). Use the Select Request data source or List Requests action to find this value. | |
| Transition ID | The ID of the transition to apply. Use the List Transitions action or the Transition data source to find available transitions. | |
| Comment | A message posted on the request when the transition is executed. Visible to the customer by default. |
Update Asset object
Updates an existing Assets/CMDB object with the supplied attributes.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Object ID | Numeric ID of the Assets object (e.g. 425). Distinct from the human-readable object key (e.g. ITAM-425). | |
| Object Type ID | ID of the object type. Use the Select Object Type data source after picking a schema. | |
| Attributes | JSON array of attribute payloads for this object. Each item has the shape { objectTypeAttributeId, objectAttributeValues: [{ value }] }. |
|
| Additional Fields | Extra request body properties to merge into the payload alongside the standard inputs. Provide a JSON object keyed by field name. |
Upload temporary file
Uploads a file as a temporary attachment for later use with Add Attachment.
| Input | Comments | Default |
|---|---|---|
| Connection | The Jira Service Management connection to use. | |
| Service Desk ID | The unique identifier of the service desk. Use the List Service Desks action or the Service Desk data source to find this value. | |
| File Contents | The contents of the file to upload. Can be a string or binary data (e.g., image or PDF) from a previous step. | |
| File Name | The filename to associate with the uploaded attachment, including the extension (e.g., report.pdf). |