Connectors
About 200 connectors for the CRM, support desk, planning and analytics tools you already run. Whatever the system, everything a connector brings in is transformed automatically: its values are standardized and every record is mapped to a node in the Product Graph, so your data sits beside the market's in the same shape.
Transformations
Salesforce calls it an account, HubSpot a company, your support desk an organization. You never write the mapping: every connector runs the same transformation on the way in, automatically, on every record.
Every record becomes one of the graph's 91 standard node types — a company, a contact, a deal, an issue, a release — whatever the source system called it.
Each field is put into one standard format: dates as ISO dates, money as an amount with its currency code, countries and phone numbers in international form, and every CRM's deal stages and ticket statuses on one shared list.
The same company or person arriving from two systems lands on one node. Companies match on domain, then LinkedIn page, then exact name; people on LinkedIn profile, then email, then name within their employer.
Each value records the system that supplied it. When two systems disagree, a rule for that field decides: fill a blank, keep the better-quality value, take the newest status, average a score or keep the highest count.
Nothing is guessed. A record of a kind the graph has no node type for yet is held for review rather than forced into the wrong one, and the original is kept, so nothing is lost while it waits.
How ingestion works
Every connector feeds the same typed graph, through the same transformation. A few of them, animated.
Ingestion
About 200 pre-built connectors pull data into the graph, standardized and mapped to its nodes, on demand.
The connector map
A selection from the catalog. Each card shows what the connector brings in and the node types its records are mapped to.
Pipeline, account, opportunity
10 connectors
Deals, contacts, companies and pipeline, matched to the accounts and people already in your graph instead of duplicating them.
HubSpot
Contacts, companies, deals, tickets, marketing email
Mapped to 20 node types
Library, proposal, battlecard
7 connectors
Bring in your existing content and proposal libraries, so they sit beside the live graph when your team answers an RFP in Accounts › Opportunities.
Roadmap, release, analytics, code
14 connectors
Roadmap, release, and analytics data normalized across the tools your PM and engineering teams already use.
Aha!
Strategy, ideas, features, releases
Mapped to 15 node types
Channels, messages, calendars, meetings
9 connectors
Messages, meetings and calendars from the tools your teams talk in, each record mapped to a node like any other.
Microsoft Teams
Channels, chats, meetings, files
Mapped to 9 node types
Email digests
Category roll-ups by email (scheduled sends are paused today)
Mapped to 1 node type
MCP, model providers, internal copilots
7 connectors
How the graph reaches the AI tools your teams already use. Availability differs by tool — ask us about yours.
SSO, SCIM, audit
5 connectors
Single sign-on and user provisioning from your identity provider. Row-level security keeps each company's data private to it.
The 2,000+ signal sources behind the public graph
11 connectors
The Product Graph is enriched from review networks, public registers, vendor sites, and the open SEC / patent / hiring corpus, on demand.
