---
title: "Jira Service Desk connector for agents — authorization and setup — AgentSky"
description: "Work with Jira Service Desk-specific entities, such as requests. Connect Jira Service Desk to AgentSky with managed OAuth."
url: https://agentsky.dev/connectors/jira_service_desk
---

# Jira Service Desk

Work with Jira Service Desk-specific entities, such as requests. Connect your account through managed OAuth to use the available operations in an agent task.

[Repo](https://agentsky.dev/auth/start?returnTo=%2Fconnectors%2Fjira_service_desk%3Fresume%3D1)

Connect Jira Service Desk using the Connectors control before sending. Authorization opens separately and your draft stays here.

Setup

## Connect Jira Service Desk with an explicit scope.

You need an AgentSky account and authority to connect the application account. Start with a read-only task before allowing changes.

01

### Find the application

Open connector settings and search for Jira Service Desk. If the catalog is unavailable, retry its load; an unavailable list is not proof the app is unsupported.

02

### Review authorization

Review the Jira Service Desk account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

### Verify a bounded task

Name one Jira Service Desk resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission.

Verify access and results

## A connected account is the start of the workflow.

Open the same resource in Jira Service Desk and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

- Access troubleshooting If Jira Service Desk access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
- Available actions The runtime discovers the connector's current operations and input requirements. Do not assume every feature in the application's website is available as an agent action.
- Authorize changes explicitly For writes, specify the target and the allowed change. An instruction to draft or analyze is not permission to publish, send or delete.

## Jira Service Desk connector questions

## Related resources

[Claude Code + Jira Service DeskUse Jira Service Desk with Claude Code in the shared Composer.](https://agentsky.dev/agents/claude-code/connectors/jira_service_desk) [Codex + Jira Service DeskUse Jira Service Desk with Codex in the shared Composer.](https://agentsky.dev/agents/codex/connectors/jira_service_desk) [OpenClaw + Jira Service DeskUse Jira Service Desk with OpenClaw in the shared Composer.](https://agentsky.dev/agents/openclaw/connectors/jira_service_desk) [OpenCode + Jira Service DeskUse Jira Service Desk with OpenCode in the shared Composer.](https://agentsky.dev/agents/opencode/connectors/jira_service_desk) [Hermes + Jira Service DeskUse Jira Service Desk with Hermes in the shared Composer.](https://agentsky.dev/agents/hermes/connectors/jira_service_desk) [Kimi Code + Jira Service DeskUse Jira Service Desk with Kimi Code in the shared Composer.](https://agentsky.dev/agents/kimi-code/connectors/jira_service_desk) [DeepSeek Harness + Jira Service DeskUse Jira Service Desk with DeepSeek Harness in the shared Composer.](https://agentsky.dev/agents/dsh/connectors/jira_service_desk) [pi + Jira Service DeskUse Jira Service Desk with pi in the shared Composer.](https://agentsky.dev/agents/pi/connectors/jira_service_desk) [All connectorsUnderstand managed application access.](https://agentsky.dev/connectors) [ChannelsChoose where the agent conversation happens.](https://agentsky.dev/channels) [PricingReview charges before running work.](https://agentsky.dev/pricing)

## Connect the right Jira Service Desk account.

[Open connector settings](https://agentsky.dev/connectors)

## Frequently asked questions

### How do I connect Jira Service Desk to AgentSky?

Sign in to AgentSky, open Connectors in the Composer and search for Jira Service Desk. Choose Connect, complete the provider's authorization flow, and return to your draft. Check that the intended account appears as connected before sending.

### Do I need a Jira Service Desk API key?

This listing uses managed OAuth. Authorize the account in the provider's flow; do not paste a password or API key into the Composer. Any account, plan or administrator requirements are determined by Jira Service Desk.

### What can my agent do in Jira Service Desk?

The runtime discovers current operations and their required inputs. A catalog listing does not promise every feature of Jira Service Desk. Start by asking which operation supports your task, and specify the resources and changes you authorize.

### Does connecting Jira Service Desk make agent tasks free?

No. Account authorization and task usage are separate. AgentSky bills compute and model usage according to its pricing. Any Jira Service Desk subscription, API quota or provider charge remains separate; review those limits before running a task.

---

Markdown copy of https://agentsky.dev/connectors/jira_service_desk. Every agentsky.dev page has one: add `.md` to its address or send `Accept: text/markdown`. Start from https://agentsky.dev/llms.txt.
