Home / Integrations / Roam Research

Integration · Productivity and Collaboration

Connect Roam Research networked notes to Salesforce Agentforce

Roam Research is the networked note-taking application that organises knowledge as a bidirectional graph — where every note is a node, every reference creates a link, and the full context of a topic emerges from the network of connections rather than a hierarchical folder structure. For researchers, strategists, and commercial professionals who use Roam as their personal knowledge graph, the account knowledge in Roam is structured differently from a conventional note application: a customer's page connects to the meeting notes that reference it, the competitor analysis that mentions their name, the market research that contextualises their industry, and the strategic framework notes that inform the commercial approach. When Emerge Digital connects Roam Research to Agentforce, the networked knowledge graph about a customer account is available to agents during commercial conversations — surfacing the connected context that a hierarchical note-taking system would not link.

All integrations

What this unlocks

  • Bidirectional link graph retrieval for deep account context: Roam's bidirectional links mean that querying a customer's page surface not only what was written directly about the customer, but every note that references the customer — meeting notes that mention them, research pages that discuss their industry, competitive analysis that references their positioning. An agent can retrieve this full connected context during account preparation rather than a linear set of notes.
  • Daily note meeting references for chronological account history: Roam users typically capture meeting notes on dated daily note pages, with customer references creating bidirectional links back to the customer's page. An agent can retrieve the chronological meeting history for a customer account by querying the daily note references on the customer's Roam page — providing a complete timeline of interactions captured in the personal knowledge graph.
  • Research and context nodes for commercial preparation: Roam users often maintain research pages — industry analysis, competitor positioning, market context — that reference multiple customer accounts and strategic themes. An agent can retrieve the research nodes relevant to a customer's industry or competitive context during sales preparation, surfacing the background intelligence that informs the commercial approach.
  • Salesforce commercial events create Roam customer pages: when a new prospect is added to Salesforce or a new commercial opportunity opens, an Agentforce agent can create the corresponding Roam customer page with the Salesforce account details — establishing the knowledge graph node for the account before the first meeting, ready for the account manager to add meeting notes and research connections.

In the customer journey

Bidirectional link graph surfaces unexpected account connection

An account manager is preparing for a first meeting with a new enterprise prospect. The agent queries the account's Roam page and its bidirectional link graph — the prospect's name appears in a research note about digital transformation initiatives in their vertical, in a competitor analysis note about two other vendors the prospect was known to be evaluating, and in a market size estimate that was used in a prior proposal for a different prospect in the same industry. The account manager enters the meeting with the pre-existing industry context and competitive intelligence rather than starting the account from a blank Salesforce record.

Daily note timeline reconstructs account meeting history

An account manager is reviewing a long-standing customer relationship ahead of a senior leadership meeting. The agent queries the customer's Roam page for all references in daily note pages — retrieves 14 daily notes referencing the customer over 18 months. The chronological list of daily note references traces the full conversation history: initial discovery, proof of concept discussions, contract negotiations, implementation updates, and renewal conversations. The account manager has the complete meeting history without a formal CRM note for each interaction.

New prospect in Salesforce creates Roam account page

A new enterprise prospect is added to Salesforce following a referral. An Agentforce agent creates the corresponding Roam page for the prospect, pre-populated with the Salesforce account name, industry, annual revenue estimate, primary contact, and the opportunity stage. The Roam page is ready for the account manager to begin adding meeting notes, research connections, and strategic context — with the basic facts from Salesforce already in place before the first interaction.

Why not a conventional note-taking integration?

Conventional note-taking integrations retrieve specific notes by folder, notebook, or tag — they return the notes that were written directly about a topic. Roam's integration returns the network of connections: not only the customer's own page, but the research, competitor analysis, and market intelligence that links to them. For strategists and commercial professionals who organise knowledge as a graph rather than a folder hierarchy, the bidirectional link retrieval is what makes the integration qualitatively different from an Evernote or OneNote integration — it surfaces the connected context that hierarchical note systems cannot navigate.

Roam Research's Agentforce integration is most relevant for individual commercial strategists, enterprise account managers, and sales leaders who use Roam as their primary personal knowledge graph and whose account knowledge is structured as a bidirectional link network rather than a conventional hierarchical note system. It is a specialist integration for organisations where the knowledge management philosophy aligns with Roam's networked approach.

How Emerge integrates Roam Research

Emerge Digital connects Roam Research to Salesforce Agentforce as a consulting engagement. We design the bidirectional link graph query layer that retrieves the full connected context for a customer account, map the Roam daily note chronology to Salesforce account history, configure the Salesforce new account trigger for Roam page creation, and integrate the networked knowledge retrieval into commercial preparation workflows.

How we structure an engagement

FAQ

Roam Research is primarily a personal tool — can it be used in team commercial contexts?

Roam Research has team multiplayer capabilities for shared graphs. The integration can work with both personal and shared team Roam graphs, with the access model reflecting the graph sharing permissions. For personal graphs, the integration accesses the individual account manager's knowledge network. For shared team graphs, the integration accesses the collective account team's knowledge structure.

We use Obsidian, LogSeq, or Notion rather than Roam — can the same networked note pattern work?

Yes. The networked note-taking integration pattern — bidirectional link context retrieval for commercial conversations, new account trigger for knowledge node creation — applies to Obsidian, LogSeq, and other graph-based note-taking tools. Notion's link structure is more linear, but the page-level retrieval pattern applies there too. Emerge builds to the knowledge management tool your team uses.

How does the integration handle the daily note structure that Roam uses for meeting capture?

Roam's daily note structure creates a chronological log of activity. The integration queries the backlinks on a customer's page to identify all daily notes that reference the customer, reconstructing the meeting chronology from the bidirectional link graph. This provides a timeline of interactions without requiring the account manager to organise their meeting notes in a dedicated customer folder.

How long does a Roam Research + Agentforce integration take?

A focused engagement typically runs three to five weeks: designing the bidirectional link graph query layer for customer account context retrieval, mapping the daily note chronology to account history, configuring the Salesforce new account trigger for Roam page creation, and testing graph context retrieval, daily note timeline reconstruction, and account page creation scenarios.

Ground your agents in Roam Research.

Tell us what your agents need to read and write in Roam Research, and we'll design the integration and the governance around it.

Talk to the practice

Prefer email? Write to the practice instead.