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.
Loading
Viktor is an AI employee that connects to Jira Service Desk in one click via OAuth 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 in Slack or Microsoft Teams; Viktor does the work in Jira Service Desk and reports back. Setup takes about two minutes.
Free to start · No credit card · SOC 2 Type 1 · Works in Slack & Microsoft Teams
Messages you'd actually send. Paste one into Slack or Microsoft Teams, 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, in Slack or Teams
“Draft replies to the open tickets in Jira Service Desk and queue them for my approval.”
— you, in Slack or Teams
“Pull this week's ticket volume and response time from Jira Service Desk every Monday.”
— you, in Slack or Teams
“Watch Jira Service Desk for tickets that mention churn and alert me immediately.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right Jira Service Desk actions, runs the work, and reports back. No workflows to build.
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"}}.
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.
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.
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).
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.
Retrieves available options for the Cloud ID field.
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).
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).
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.
Creates a new customer request.
Creates a new incident request in a Jira Service Desk. Auto-discovers the best-matching request type (prefers types named 'incident' or 'problem') and, if serviceDeskId is omitted, auto-discovers it from the user's existing requests. Use List Sites first to obtain the required cloudId. serviceDeskId is optional — if not provided, the tool calls List My Requests to discover it automatically. Returns the new request including its issueKey and issueId.
Create a comment on a customer request.
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.
Message Viktor in Slack like you'd message a teammate. "Summarize today's open tickets in Jira Service Desk and flag the urgent ones." "Draft replies to the open tickets in Jira Service Desk and queue them for my approval." Plain English, any tool.
Viktor opens Jira Service Desk, 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.
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 that agent: an AI employee that works in Jira Service Desk on your behalf and delivers the finished result in Slack or Microsoft Teams.
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.
Work with Jira Service Desk-specific entities, such as requests.
One-click OAuth - Viktor never sees your password, and you can revoke access at any time.
Review-first approvals: sensitive Jira Service Desk actions wait for your sign-off before they run.
Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models.
SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress.
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 Slack or Microsoft Teams - no workflow builder, no code.
Ask for outcomes that span tools — Viktor pulls from Jira Service Desk, cross-references the rest of your stack, and delivers one finished result.
Viktor connects to 3,200+ tools and works across them in a single run.
