Step 1: Connect your stack
27 native integrations. 3,200+ tools via managed connectors. Most are one-click OAuth, some use API keys - Viktor handles auth and starts working. No webhooks, no Zapier zaps.
Jira Service Desk AI employee
Viktor is an AI employee that connects to Jira Service Desk and helps you triage and resolve customer support tickets, running 12 Jira Service Desk actions for you like List Sites, Get Request, and Create Request. Ask in plain English from your workspace; Viktor does the work in Jira Service Desk and reports back. Viktor connects in one click via OAuth.
Works in Slack & Microsoft Teams
What is a Jira Service Desk AI agent?
A Jira Service Desk AI agent is an AI that connects to your Jira Service Desk account and completes work in it - it doesn't just answer questions about Jira Service Desk, it takes the actions. Viktor is an AI employee that works in Jira Service Desk on your behalf and delivers the finished result to your workspace.
Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Jira Service Desk actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
About Jira Service Desk
Work with Jira Service Desk-specific entities, such as requests.
You ask in your workspace
Describe what you need in plain English
Viktor picks the actions
Selects from 12 Jira Service Desk actions, chains them together
Runs in Jira Service Desk
Helps you triage and resolve customer support tickets - your real data.
Reports back
Delivers the finished result to your workspace
Try asking Viktor
What can you ask Viktor to do in Jira Service Desk?
Messages you'd actually send. Paste one into your workspace, swap in your specifics, and Viktor takes it from there.
“Summarize today's open tickets in Jira Service Desk and flag the urgent ones.”
— you, to @Viktor
“Draft replies to the open tickets in Jira Service Desk and queue them for my approval.”
— you, to @Viktor
“Pull this week's ticket volume and response time from Jira Service Desk every Monday.”
— you, to @Viktor
“Watch Jira Service Desk for tickets that mention churn and alert me immediately.”
— you, to @Viktor
How it works
How does Viktor work with Jira Service Desk?
Maya Patel11:32 AM
@Viktor check this week's Stripe revenue against HubSpot and flag anything off before the board call.
ViktorApp11:33 AM
On it. Cross-checking Stripe against HubSpot and fixing anything that doesn't line up before your board call.
Step 2: Tell Viktor what you need
Message Viktor in Slack like you'd message a teammate. "Reconcile this month's invoices and flag anything weird." "Pause Meta campaigns above $40 CPA and move the budget to winners." Plain English, any tool.
ViktorApp9:12 AM
📊 Revenue check:
$84,210 (+6.4% WoW).
3 deals didn't match HubSpot.
Fixed 2, one needs your call.
$84,210 (+6.4% WoW).
3 deals didn't match HubSpot.
Fixed 2, one needs your call.
revenue_raport.pdf
Step 3: Viktor operates, you review
Viktor opens the tools, runs the work, and posts back what changed. Sensitive actions wait for your approval. Everything is logged. You stop doing the work and start reviewing it.
Actions
What can Viktor do in Jira Service Desk?
Ask in plain English from your workspace. Viktor picks the right Jira Service Desk actions, runs the work, and reports back. No workflows to build.
- Other
Update Issue Fields
Updates fields on an existing Jira Service Desk request via the Jira platform API. Use this to change the summary, priority, description, or other fields after a request has been created. Use List Sites first to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42). fields is a JSON object of field name-value pairs. Example: {"summary": "Updated title", "priority": {"name": "High"}}.
- Other
Transition Request
Transitions a Jira Service Desk request to a new workflow status. Use List Request Transitions first to get valid transitionId values for the request. Use List Sites to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42). Optionally include a comment to explain the transition.
- Other
List Sites
Returns all Atlassian cloud sites accessible to the authenticated user. Call this tool first to obtain the cloudId (returned as id) required by every other Jira Service Desk tool. Each site includes its id (cloudId), name, and url.
- Other
List Request Transitions
Lists the available workflow transitions for a Jira Service Desk request — returns each transition's id and name. Call this before Transition Request to obtain valid transitionId values. Use List Sites first to obtain the required cloudId. Use List My Requests or Get Request to find the issueKey (e.g. IT-42).
- Other
List My Requests
Lists Jira Service Desk requests owned or participated in by the current user. Defaults to open requests owned by the current user. Use List Sites first to obtain the required cloudId. Each result includes issueKey, issueId, and request field values (summary, status). requestStatus: OPENREQUESTS (default), CLOSEDREQUESTS, or ALLREQUESTS. requestOwnership: OWNEDREQUESTS (default) or PARTICIPATEDREQUESTS.
- Other
List Cloud ID Options
Retrieves available options for the Cloud ID field.
- Request
Get Request
Fetches the full details of a Jira Service Desk request including its field values and complete comment thread in a single response. Use this to summarize a ticket without needing follow-up calls. Use List Sites first to obtain the required cloudId. Use List My Requests to find the issueKey of a request (e.g. IT-42).
- Other
Get Request Status
Returns the status history of a Jira Service Desk request — the current status plus all previous states with timestamps. Use this to understand how a request has progressed through the workflow. Use List Sites first to obtain the required cloudId. Use List My Requests to find the issueKey (e.g. IT-42).
- Other
Get Current User
Returns the authenticated user's accountid, displayname, and email from Atlassian. Use this to identify who is logged in, or to filter requests by the current user's accountid. No cloudId required — this uses the Atlassian Identity API directly.
Works with your stack
Viktor uses Jira Service Desk together with your other tools
Ask for outcomes that span tools - Viktor pulls from Jira Service Desk, cross-references the rest of your stack, and delivers one finished result.
Related
More Productivity integrations
Viktor connects to 3,200+ tools and works across them in a single run.
Trusted by 63,000+ teams
The moment Viktor becomes part of the team.
Jira Service Desk integration FAQ
Yes. Jira Service Desk is one of the 3,200+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Jira Service Desk from their workspace - no workflow builder, no code.
4.9 on G2G2 rating: 4.9 out of 5 stars
One hire. The output of a team.
Viktor works nights, remembers every decision, and connects to 3,200 tools. Start free with $100 in credits, then $50 a month.