Integrations
Connect Kansov to Jira (two-way sync + push), Slack (capture messages as Insights & Tasks), Salesforce, Zoho Desk, Google Calendar, Outlook, ICS feeds, the Browser Extension, and AI assistants like Claude. Step-by-step setup for each.
Color key: Blue steps happen inside Kansov. Green steps happen inside the external application or service.
Jira Cloud Integration
Kansov connects bi-directionally to Jira Cloud. Sync tickets from Jira into Kansov as Insights (customer signal flows in), and push Kansov Features to Jira as Epics (engineering handoff flows out). Both directions are optional and configured independently.
Jira Cloud only. Server and Data Center are not supported. Admin access to both Jira and Kansov is required to set up the integration.
Step 1 — Create the OAuth app in Atlassian
Done once per workspace. These steps happen in Atlassian's Developer Console, outside Kansov.
Go to developer.atlassian.com → My Apps → Create → OAuth 2.0 integration. Give it a name (e.g. "Kansov"). Note the Client ID and Client Secret — you'll paste both into Kansov in Step 2.
Under Authorization, set the Callback URL to: https://[your-kansov-domain]/api/integrations/jira/callback
Under Permissions → Jira platform REST API → Configure:
read:jira-work&read:jira-user— required to sync Jira issues into Kansovoffline_access— required so tokens can refresh; without it, the integration breaks every hourwrite:jira-work— only required if you want to push Kansov Features to Jira as Epics. Skip if you only need inbound sync.
If you add write:jira-work later to an already-connected workspace, you'll need to disconnect Jira in Kansov and reconnect — Atlassian only grants newly added scopes on a fresh authorization.
Step 2 — Connect in Kansov
Go to Settings → Integrations & MCP → Integrations, find the Jira card, click Configure credentials. Paste the Client ID and Client Secret from Atlassian, then Save.
Kansov redirects you to Atlassian to authorize the app. Approve it; you'll be bounced back to Kansov with the integration marked as Active.
Step 3 — Configure sync (Jira → Kansov Insights)
In the Jira integration card, click Configure. For each Jira project you want to sync, pick:
- Issue types — which ticket types to pull (Bug, Story, Feature Request, Emailed request, etc.). Different projects can have different selections.
- Labels (optional) — when set, tickets matching any selected issue type or any label from this project are synced. Useful for pulling only specifically-tagged work from a dev project.
Also in the same sheet, configure Field mappings:
- Company — maps a Jira field to Kansov's Customer. For Service Desk projects, Organizations works; for software projects, Components or Project Name.
- Customer Email — set to Reporter to pull the ticket reporter's email onto the Kansov Insight.
- Auto-create company — when on, a new Kansov customer is created if the mapped company name isn't already present.
Save. Kansov will sync hourly, or click Sync Now for an immediate run. Each Jira ticket that matches your filter becomes a Kansov Insight with an Origin card linking back to the source ticket.
Step 4 — (Optional) Enable push: Kansov Feature → Jira Epic
If you want your PMs to hand off Kansov Features to engineering as Jira Epics in one click, enable push in the same Configure sheet:
In Settings → Integrations & MCP → Integrations → Configure (Jira), scroll to the Push features to Jira section. Toggle it on.
All Epics created from Kansov Features land in this one project. You can change it later; existing pushed Features keep their original Epic link.
Comma-separated. These labels are added to every Epic created from Kansov, in addition to the always-applied from-kansov marker. Handy for sprint planning filters (e.g. product-backlog, q1-roadmap). Don't re-type from-kansov — it's added automatically.
After saving, any user with write access on Features (Admin, PM, or Contributor roles) will see a Create Jira Epic button on the Feature detail view. Viewers cannot push.
What happens when a user clicks "Create Jira Epic"
- A new Epic is created in your configured Jira project with the Feature's title and description.
- The Epic is labeled
from-kansov(plus any defaults you configured) so you can find all Kansov-originated Epics with a JQL query:labels = "from-kansov". - The Epic's Reporter is set to the Kansov user who clicked, if their email matches an Atlassian account on your tenant. If no match, Reporter falls back to the user who connected Kansov to Jira.
- Jira's Web Links section on the Epic carries a clickable link back to the Kansov Feature — so engineers can navigate between the two.
- In Kansov, the "Create Jira Epic" button is replaced with an Origin card showing the Jira Epic key, live status, priority, and an "Open in Jira" button.
How Jira status stays in sync on the Kansov side
Kansov automatically refreshes the Epic's status and priority from Jira once an hour, and also on any manual Sync Now. The refresh only updates display-only fields on the Origin card — it does not change the Kansov Feature's own status. PMs stay in control of the Feature record; engineers stay in control of the Epic.
Tip — auditability. Because every pushed Epic is labeled from-kansov, your engineering leads can pull a monthly report of "everything requested via Kansov" with a one-line JQL filter. Combined with the Web Link back to Kansov, this gives clean bidirectional traceability from customer signal to engineering delivery.
Slack
Capture customer signal directly from Slack. From any message, your team can save it as an Insight or turn it into a Task — and scan a whole channel for insights over a recent window. Signals land in Kansov attributed to the person who captured them, with a link back to the original Slack message.
One-click connect. Unlike Jira, Salesforce, and Zoho Desk, Slack needs no external app setup — you don't create anything on api.slack.com. An admin just clicks Add to Slack and approves. Kansov runs a single verified Slack app for all customers; your workspace's data stays fully isolated.
Step 1 — Connect Slack
Go to Settings → Integrations & MCP → Integrations, find the Slack card, and click Add to Slack. (Admin only.)
Slack shows the permissions screen — click Allow. You're bounced back to Kansov with Slack marked Connected. Some Slack workspaces require an admin to approve new apps first; Slack handles that automatically.
In each channel, type /invite @Kansov. This is required for Kansov to read a thread's replies or scan a channel. Single messages and tasks work without it.
Step 2 — Capture from Slack
Every member of your Slack workspace gets these immediately — no per-user setup:
- Save as Insight — on any message, open the ⋯ More actions menu → Save as Insight. A single message becomes one Insight. If the message is part of a thread, click Summarize & extract to have AI pull every distinct insight from the whole thread into a checklist — tick the real ones, edit if needed, and save.
- Create Task — ⋯ More actions → Create Task creates a to-do (assigned to you) with a link back to the Slack message. No AI, instant.
- Scan a channel — type
/kansovscanin a channel, pick a window (last 1, 3, or 7 days), and Kansov reads the channel — including thread replies — and returns a checklist of insights to review and save.
Sharper AI results. Fill in your Product Profile at Settings → Workspace (product name, aliases, description, competitors). Kansov injects it into every extraction so insights are correctly tagged as being about your product vs. a competitor or an internal tool.
Note. The bot must be invited to a channel to read its threads or scan it. Direct messages and Slack Connect (external) conversations can't be scanned, but you can still Save as Insight on an individual message there. Anyone in your connected Slack workspace can capture into Kansov; captures are attributed to the matching Kansov user by email, or to the admin who connected Slack if there's no match.
Salesforce
Import your Salesforce Accounts into Kansov's Customer Repository, so Insights and Ideas reflect real customers with segment, status, and revenue. One-way sync (Salesforce → Kansov).
Admin only, BYOK. Each workspace connects its own Salesforce Connected App. Kansov pulls Accounts only (not Contacts or Opportunities) and never writes back to Salesforce.
Step 1 — Create a Connected App in Salesforce
Go to Setup → App Manager → New Connected App. Enable OAuth Settings.
Callback URL: https://[your-kansov-domain]/api/integrations/salesforce/callback. Add OAuth scopes api (read Accounts) and refresh_token (keeps the sync alive when sessions expire). Save.
Open the app → Manage Consumer Details → copy the Consumer Key (Client ID) and Consumer Secret (Client Secret). Connected Apps take a few minutes to activate. For sandbox orgs, use the test.salesforce.com login host.
Step 2 — Connect & configure in Kansov
In Settings → Integrations → Salesforce, click Setup, paste the Consumer Key and Consumer Secret, and click Save & Connect. Approve access on Salesforce; an initial sync starts automatically.
Click Configure mapping to map a Salesforce Account field to Kansov Segment, Status, and Revenue (revenue defaults to AnnualRevenue). Unmapped picklist values are reported after each sync so you can fill them in.
Salesforce syncs every 30 minutes; use Sync now for an immediate run, the Active/Paused toggle to pause without disconnecting, and Disconnect to remove all Salesforce data and tokens. Up to 2,000 Accounts sync per cycle; larger orgs resume on the next cycle.
Zoho Desk
Import your Zoho Desk tickets as Insights so customer problems flow straight into discovery — optionally with an AI-generated summary of each ticket's conversation. One-way sync (Zoho Desk → Kansov).
Admin only, BYOK, region-specific. Zoho runs multiple data centers (US, EU, IN, AU, JP, CA, SA). Create your API app in the same region as your Zoho Desk account, and pick that data center when connecting.
Step 1 — Create a Server-based app in Zoho
Go to your region's API console (api-console.zoho.com, .eu, .in, …) and create a Server-based Application.
Authorized Redirect URI: https://[your-kansov-domain]/api/integrations/zoho-desk/callback. Copy the Client ID and Client Secret. (Kansov requests the Desk.tickets.READ, Desk.basic.READ, Desk.contacts.READ, and Desk.settings.READ scopes during connect.)
Step 2 — Connect & configure in Kansov
In Settings → Integrations → Zoho Desk, click Setup, select the Data center that matches your Zoho account, paste the Client ID and Client Secret, and click Save & Connect. Approve access on Zoho.
Click Configure to choose which departments, ticket statuses, and ticket types to sync, and to map Zoho fields to Kansov company, customer email, product area, and module (custom cf_* fields supported). Toggle Auto-create customers to add new customers when a company isn't found.
Turn on AI summary of ticket conversations to have Kansov summarize each ticket's subject, description, and comments into a short summary on the Insight. Uses your workspace's configured AI provider (OpenAI or Gemini). Off by default.
Zoho Desk syncs every 60 minutes (incremental); Sync now runs a full re-pull and regenerates AI summaries. Up to 2,000 tickets sync per cycle; larger volumes resume on the next cycle. Each ticket becomes an Insight linked back to the source ticket.
MCP Server (Claude Desktop & Cursor)
Kansov exposes an MCP (Model Context Protocol) server that lets AI assistants like Claude Desktop and Cursor read and write your Kansov data using natural language commands.
Go to Settings → Integrations & MCP → MCP Clients. Click Generate Token. Copy the token and note your MCP server URL.
Open Claude Desktop settings → Developer → Edit Config and add a server entry with your Kansov MCP URL and token.
Restart Claude Desktop. Try: "List my 5 most recent Insights in Kansov".