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 & Confluence natively and helps you plan, assign, and track project tasks, running 41 Jira & Confluence actions for you like Fetch, Search, and Jira read. Ask in plain English in Slack or Microsoft Teams; Viktor does the work in Jira & Confluence 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.
“Create tasks in Jira & Confluence from the action items in this thread.”
— you, in Slack or Teams
“Summarize what changed in Jira & Confluence this week and post it here every Friday.”
— you, in Slack or Teams
“Find the tasks in Jira & Confluence that are overdue and draft a status update.”
— you, in Slack or Teams
“Keep Jira & Confluence in sync with our roadmap and flag anything at risk.”
— you, in Slack or Teams
Ask in plain English in Slack or Microsoft Teams. Viktor picks the right Jira & Confluence actions, runs the work, and reports back. No workflows to build.
Get child pages of specified page.
Jira read operations (e.g. get issue link types).
Get current user info.
Get cloudId to make tool calls. When a link is provided (e.g. try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources.
Get issue types.
Get remote links.
Get projects.
Get transitions.
Transition issue status.
Lookup user IDs.
Get spaces.
Jira write operations (e.g. create issue link).
Create a new Compass component.
Get a Compass component by ID.
Create a relationship between Compass components.
Get a list of Compass custom field definitions.
Create a custom field definition in Compass.
Get a list of Compass components.
Search Jira and Confluence using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context.
Get available Jira issue link types (e.g. Blocks, Duplicate, Clones, Relates). For createIssueLink: inwardIssue = blocker, outwardIssue = blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A).
Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content.
Search Jira and Confluence using Rovo Search, ALWAYS use this tool to search for Jira and Confluence content unless the word CQL or JQL is used in the context.
Get details of a Jira issue or Confluence page by ARI (Atlassian Resource Identifier), if the id is not an ARI, then use a different tool to fetch the content.
Get reply(child) comments for a comment.
Add or update a worklog on a Jira issue. When worklogId is provided, updates that worklog.
Get footer comments for a page or blog post.
Update a Confluence page or blog post.
Create a link between two Jira issues. For directional link types (e.g. Blocks): inwardIssue = issue that blocks, outwardIssue = issue that is blocked (e.g. "A is blocked by B" → inwardIssue: B, outwardIssue: A). Use getIssueLinkTypes if link type is unknown.
Add or update a comment on a Jira issue.
Search Confluence content (pages, blog posts, comments, attachments) using CQL (Confluence Query Language). CQL is specific to Confluence and is not interchangeable with JQL.
Get issue details.
Get inline comments for a page or blog post.
Create a footer comment on a page or blog post.
Create an inline comment on specific text in a page or blog post. For top-level comments, provide pageId and inlineCommentProperties (text selection + match counts). For replies, provide parentCommentId only (no pageId or inlineCommentProperties). You must first fetch the page content (e.g. using getConfluencePage) to find the exact text and count how many times it appears. Incorrect or missing inlineCommentProperties can result in a 400 error from the Confluence API.
Get field metadata.
Create a Jira issue. Use additionalfields to set any Jira field that does not have its own parameter (e.g. custom fields, priority, components).
Get a Confluence page or blog post by ID, including body content.
Update issue. After updating, returns the issue using the same default read fields as getJiraIssue (summary, description, status, issuetype, priority, labels, components, assignee, reporter, created, updated, resolution, project). Use getJiraIssue with fields ["all"] or a custom list if you need more.
Create a Confluence page or blog post.
Search issues with JQL, total counts only when explicitly requested.
Get pages or blog posts in a space.
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. "Create tasks in Jira & Confluence from the action items in this thread." "Summarize what changed in Jira & Confluence this week and post it here every Friday." Plain English, any tool.
Viktor opens Jira & Confluence, 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 & Confluence AI agent is an AI that connects to your Jira & Confluence account and completes work in it - it doesn't just answer questions about Jira & Confluence, it takes the actions. Viktor is that agent: an AI employee that works in Jira & Confluence 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 & Confluence actions, chains them with the other 3,200+ tools it connects to, and asks for approval before anything sensitive runs.
Manage issues, projects, and collaborate on documentation
Native integration - Viktor handles authorization itself, never sees your password, and you can revoke access at any time.
Review-first approvals: sensitive Jira & Confluence 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 & Confluence is one of the 3,200+ tools Viktor connects to, as one of Viktor's native, deepest integrations. Once connected, anyone on your team can put Viktor to work in Jira & Confluence from Slack or Microsoft Teams - no workflow builder, no code.
Ask for outcomes that span tools — Viktor pulls from Jira & Confluence, 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.
