Integrations
Connect the places your users already talk. Every answer Kinn gives is grounded in the sources you choose.
An integration is any place Kinn reads from. Integrations are the input to everything Kinn does. Without at least one, there's nothing to query.
How integrations connect
Integrations come in two broad shapes, depending on whether you're pointing Kinn at a space you control or at public content anyone can see.
Spaces you own or control. For these you grant Kinn access and then choose the slice it can see — channels in Discord or Slack, your Jira projects, or your GitHub repositories. Email works by forwarding messages from an inbox you already use. Imported Data works by uploading exports from custom sources. Kinn only sees what you've explicitly connected, forwarded, or uploaded.
Public content you point Kinn at. For these there's nothing to own — you just tell Kinn what to follow: subreddits on Reddit, channels or playlists on YouTube, social posts or profiles, or an app's store listing. These public sources need no account connection.
Either way the principle is the same: you decide exactly what Kinn watches, and it watches nothing else.
Reading vs. writing
Most integrations are read-only — Kinn ingests what's there and never changes it. A few are two-way: on top of reading, Kinn can write back. Jira is the clearest example — Kinn can create and update issues in the projects you connect, which is how a bug surfaced in your community becomes a tracked ticket.
Two-way integrations can make changes in the connected system. They're always scoped to what you've connected (for example, specific Jira projects), and each integration's page spells out exactly what it can and can't do.
At a glance
| Integration | How you connect it | You scope it to | Direction |
|---|---|---|---|
| Discord | Authorize a bot in your server | Channels | Read-only |
| Slack | Install the Kinn app | Channels | Read-only |
| Create a private forwarding address | Existing inboxes | Read-only | |
| Imported Data | Upload a data file | Named collections | Read-only |
| Paste a public URL | Subreddits or individual posts | Read-only | |
| YouTube | Paste a public URL | Channels, playlists, videos | Read-only |
| TikTok | No account needed | Video URLs | Read-only |
| No account needed | Post and Reel URLs | Read-only | |
| X (Twitter) | No account needed | Profiles or individual posts | Read-only |
| Steam | No account needed | Games by store URL | Read-only |
| App Store | By store URL (+ optional API key) | iOS and Mac apps | Read-only |
| Google Play | By store URL (+ optional authorization) | Android apps | Read-only |
| Meta Quest | By store listing | Experiences | Read-only |
| Jira | Authorize via Atlassian | One Jira Cloud site | Two-way |
| GitHub | Install the GitHub App | Selected repositories | Read-only |
| Website | Enter your site URL | Your own site / blog | Read-only |
How syncing works
When you first connect an integration, Kinn pulls in a window of recent history so you have something to query right away. After that, it keeps up with new activity in the background.
How far back the initial sync reaches, and how quickly new activity shows up, varies by integration — each integration page notes the specifics.
Why connect more than one
Kinn's answers are only as complete as the integrations behind them. Connecting more integrations doesn't just add volume — it lets Kinn connect signal across them. A bug that shows up in your Discord, your subreddit, and your GitHub issues at once is a very different priority than one mentioned in a single stray comment, and Kinn can only see that pattern if all three are connected.
A common shape for a setup:
- A community integration or two (Discord, Slack, Reddit, or Steam) for what people are saying
- A support source (Email) for feedback sent directly to your team
- Imported Data for exports from tools without a dedicated integration
- A social integration (YouTube, TikTok, Instagram, or X) if creators or social posts are part of your story
- A tracker (Jira, GitHub) to tie what you learn back to your backlog
Managing integrations
Open Settings → Integrations to see the sources connected to the selected product. Choose Add Integration to add another source, or open an existing integration to change its scope or disconnect it.
Available integrations
Choose an integration to see what it pulls in, how to connect it, the permissions it needs, and the questions it unlocks.
Community & social
Discord
Live community and support conversations
Slack
Messages from selected workspace channels
Feedback forwarded from existing inboxes
Public discussion and broader sentiment
YouTube
Viewer comments across video content
TikTok
Video performance and comments
Post and Reels feedback
X (Twitter)
Public posts and engagement
Steam
Game reviews and community discussions