Documentation
Connect your tools
Integrations
Connect the tools where customer conversations, context, delivery work, and AI build workflows already happen.
AI assistants & MCP
Connect Zentrik to MCP-capable tools, then start with grounded product workflows once the connection works.
ChatGPTInstall the published Zentrik plugin, authorize one workspace, and start from a real product question.02MCP use casesStart with high-value product workflows that already map well to the Zentrik graph and MCP tools.03Use Zentrik MCP wellUse tighter, evidence-seeking prompts so your MCP tool stays anchored to the product graph.
Context management
Import or sync documentation and shared context.
Google DriveGoogle Drive supports two jobs in Zentrik: bringing explicitly chosen Docs into shared workspace context and keeping picked initiative documents synced with Google Docs when upstream collaboration needs to stay in place.NotionUse Notion as the authored source for an intent canvas or one-pager while Zentrik becomes the live initiative workspace for evidence, decisions, research, and delivery.ConfluenceUse Confluence to ground planning, delivery, and product decisions in the documentation your team already maintains upstream.
Work management
Issue trackers and delivery systems—pull context in, push execution-ready work out.
JiraUse one Jira connection to keep discovery demand, planning context, and delivery execution aligned between Jira and Zentrik.GitHubReference an idea or initiative in a pull request and Zentrik links the work automatically, so the roadmap shows what is in flight and what has shipped.SlackBring @Zentrik into Slack so useful conversations keep moving into durable product work without losing their source context.LinearUse Linear when delivery issues already hold product signal that should feed Discovery inside Zentrik.
Customer & product signal
Calls, support tickets, surveys, and upstream idea tools—the voice of your customers and market.
ZoomUse Zoom calls as discovery input so product teams can work from transcripts, excerpts, and conversation context instead of replaying recordings.Microsoft TeamsUse Microsoft Teams when customer conversations are recorded in Teams and you want transcript-driven Discovery without replaying meetings.AirtableConnect an Airtable personal access token, then map any table into Discovery — routing rows to signals or ideas and resolving linked records to the right accounts.FathomUse Fathom meetings as Discovery input so teams can work from transcript evidence without manually rewatching calls.FirefliesBring selected Fireflies transcripts into Discovery as traceable product signal.GranolaBring selected Granola notes into Discovery as source-backed transcript evidence.GongBring Gong conversations into Discovery so product teams can work from what customers and buyers actually said, with transcript context attached.ZendeskUse Zendesk tickets as structured discovery input, then control which groups and fields shape what enters Zentrik.PendoUse Pendo to bring NPS records, guide and poll context, and account identities into Zentrik. Choose a guide/poll scope, import history, link accounts, and create Discovery signals from useful comments.Aha!Use Aha! when product demand and ideas already live upstream and need to feed Discovery inside Zentrik.EmailUse the shared workspace mailbox when customer emails, escalations, or inbound threads should land in Discovery without each teammate connecting their own inbox.
CRM
Connect signal to accounts, deals, and ARR impact.
Code generation
Send product context into build, prototyping, and prompt tools.
CursorSave a shared Cursor key when implementation work should start from product context already shaped in Zentrik.Vercel's v0Save a workspace Vercel v0 token when the team wants repeatable prototype generation from initiative context, not a one-off prompt handoff.LovableUse Lovable when you want the fastest path from an initiative in Zentrik into an external prototype session.BoltUse Bolt when the team wants a fast prototype handoff from initiative context without saving credentials in Zentrik.Magic PatternsUse Magic Patterns when the team wants to explore interface directions quickly from the same initiative context already used elsewhere in Zentrik.AlloyUse Alloy when the prototype should evolve an existing product page rather than start from a blank canvas.KiroUse Kiro when the next step is an implementation-ready requirements package rather than a visual prototype.
Developer access
API keys and MCP endpoints for wiring Zentrik into other tools.
01Zentrik MCPThe short setup guide for connecting Zentrik MCP and choosing the right workspace.02Zentrik MCPThe short setup guide for connecting Zentrik MCP and choosing the right workspace.03Zentrik MCPThe short setup guide for connecting Zentrik MCP and choosing the right workspace.04Zentrik MCPThe short setup guide for connecting Zentrik MCP and choosing the right workspace.
A human path
Still not finding the answer?
Tell us what you were trying to do. We will receive this documentation section with your question.