The integrations you'll see below are examples, not requirements. Specky takes data from wherever it lives — OAuth-connected tools, internal systems via REST, webhooks from anything, files, URLs, even highlighted text from your browser. If a signal exists, you can graph it.
Doesn't matter. Those are examples of common signal sources. If your team runs on Trello + Zoom + spreadsheets + customer emails, all of that lands in the graph just the same — through the methods below.
OAuth covers the common stack. Everything else gets in via REST, webhooks, files, URLs, the browser, or the AI itself.
Native OAuth providers
One-click OAuth for 21+ common tools. None of them are required — they're just the fastest path in when you happen to use them.
Capture decisions, threads, and emails the moment they happen — without changing how anyone works.
Pages, boards, and design surfaces stay editable in-place — and queryable in chat.
Specky-generated tickets land directly in your tracker. Engineering progress flows back to the roadmap.
CRM context, call transcripts, product analytics, and error streams — citable in PRDs, watched by the autonomous agent.
Browser-based intel and social channels — none of it stays trapped in its source app.
Even before they ship natively, all of these can already feed Specky via REST, webhooks, or file import.
CRM signals → Product Graph. On the roadmap.
Ticket and chat feedback as first-class graph nodes.
Broader analytics-source coverage alongside PostHog and Pendo.
Pull design files into PRDs and roadmap items.
Microsoft document stores alongside Google Drive.
Pull existing research and feedback archives in one shot.
Yes. Those are examples we name often because they're common — they're not requirements. If you have call recordings somewhere else (Zoom, Otter, internal tool, even raw transcripts in a folder), drop them in via file upload, URL paste, or the REST API. The graph treats them identically.
Yes, through the REST API or a webhook. Push events whenever you want, format them as typed signals, and they show up in the graph alongside everything else. The Custom API connector also lets you point Specky at any REST endpoint and have it pull on a schedule.
Connect Gmail or Outlook for ongoing capture, drop CSVs in via the file upload, and paste URLs of any wiki pages you want pulled in. Specky parses, dedupes, and clusters them automatically.
Yes — every workspace gets an API key from Settings → API. Use it to POST signals, fetch the graph, run custom workflows, or expose Specky to your own internal tooling.
Yes. Drafted tickets push to Jira / Linear / GitHub / Azure DevOps; PRDs round-trip with Notion and Confluence; campaigns publish to LinkedIn and Instagram. For anything not natively supported, outbound webhooks fire on events you choose.
Connect what you have with one click. For anything else, the API, webhooks, and import tools are right there waiting. If your team uses something we haven't named, we'd still love to hear about it.