Connect collaboration to the systems that trigger the work.
When a Salesforce or HubSpot event fires, nFlow provisions a governed Teams workspace — channels, SharePoint folders, Planner tasks, and CRM record pinned as a tab.
When systems only notify, the setup still happens manually.
A deal qualifies in the CRM, and now someone has to build the Teams workspace by hand — create the channels, set up the SharePoint library, add the right people, paste in the account context — for every opportunity, every time. High-value deals get an ad-hoc room; the rest get nothing. nFlow closes that gap: the event that matters in your system of record becomes a fully structured, governed workspace the moment it happens — so teams spend their time on the work, not the setup.
nFlow provisions a workspace — a complete one, not a notification.
When a CRM trigger fires, nFlow builds a complete collaboration environment from an nBold template. Not a channel-creation request, not a tab — a structured, ready-to-work workspace.
Structured channels
Channels laid out to your sales motion — discovery, proposal, legal, onboarding — so every deal room starts with the same ready-to-work playbook.
Planner tasks
Start with the plan already in place: a Planner board with task lists per stage so the team knows what to do next the moment the workspace appears.
SharePoint documents
A SharePoint document structure with the right folders and file templates from day one — proposals, contracts, statements of work. Not a blank library.
CRM record pinned as a tab
The Salesforce opportunity or HubSpot deal pinned as a tab inside the workspace. The CRM stays the source of truth. Teams becomes where execution happens.
Membership from CRM roles
The account executive, solution engineer, and customer-success owner added automatically from their role on the CRM record — kept in sync as roles change.
Governed by default
Sensitivity labels, lifecycle, and audit logs inherited from the nBold template. Business teams move faster. IT keeps control.
From CRM event to governed workspace — one motion.
No one switches tools. The trigger fires in Salesforce or HubSpot, and the workspace is built and governed in Microsoft Teams before anyone touches it.
A CRM event fires
A new opportunity, a stage change, a record creation, or a field update in Salesforce or HubSpot — the work starts in the system your revenue teams already run on.
nFlow routes it to a template
The no-code visual flow builder maps each event to the right nBold template — deal room, deal desk, or account workspace — and sets naming and membership rules. No code, no per-deal setup.
nBold provisions over the Graph API
Through the Microsoft Graph API under a service account you control, nFlow builds the full workspace: Teams channels, a SharePoint document structure, Planner tasks, and membership — all governed before anyone opens it.
CRM context travels into Teams
The CRM record is pinned as a tab, membership stays synced to CRM roles, and the team working the deal has the same context the CRM does — without copy-paste between systems.
Beyond what the native CRM connector provides.
Microsoft’s native Salesforce app for Teams gives you notifications and record search. nFlow provisions the complete structured workspace those deals actually get worked in.
| Capability | Native CRM connector | nFlow |
|---|---|---|
| Notifications in Teams from the CRM | Yes | Yes |
| CRM record search inside Teams | Yes | Yes |
| Provision a structured workspace per deal | — | Yes |
| Channels laid out to your sales motion | — | Yes |
| Planner tasks per stage | — | Yes |
| SharePoint document structure | — | Yes |
| CRM record pinned as a tab | — | Yes |
| Membership synced from CRM roles | — | Yes |
| Governance — labels, lifecycle, audit logs | — | Yes |
| No-code flow builder for RevOps | — | Yes |
nFlow provisions through the Microsoft Graph API under a service account you control, and every provisioned workspace lives in your Microsoft 365 tenant. ISO 27001 and SOC 2 Type II certified.
Start from your CRM.
Each CRM has its own set of flows and triggers. Start with your system of record, or step back to the wider Microsoft 365 integration story.
nFlow for Salesforce
Deal rooms, account workspaces, and team-membership sync provisioned the moment an opportunity or stage change fires in Salesforce.
Explore nFlow for SalesforcenFlow for HubSpot
Deal Desk and Deal Room flows turn pipeline movement into a ready-to-work, governed Microsoft Teams workspace.
Explore nFlow for HubSpotPlatform integrations
The wider Microsoft 365 integration story — Graph API and Microsoft Forms triggers, with nFlow as the CRM layer on top.
Explore Platform integrationsFrequently asked questions
What is the difference between an integration and a notification?
A notification tells someone something happened. nFlow provisions the complete structured workspace where the work can actually happen — channels, Planner tasks, SharePoint folders, CRM context pinned as a tab, membership, and governance. That is the difference.
Which systems does nFlow connect?
nFlow connects Salesforce and HubSpot as CRM sources to Microsoft Teams, SharePoint, and Planner as the destination. A CRM event — a new opportunity, a stage change, a record creation, or a field update — provisions a structured workspace from an nBold template, governed from the moment it exists.
Does nFlow store our Salesforce or HubSpot data?
No. nFlow reads CRM events to decide when to provision and how to name and populate a workspace. Every provisioned workspace lives in your Microsoft 365 tenant. nBold is ISO 27001 and SOC 2 Type II certified.
How does nFlow reach Microsoft Teams and SharePoint?
Through the Microsoft Graph API, under a service account you control inside your own tenant. The same connection lets nFlow build channels, a SharePoint document structure, Planner tasks, and membership — and apply guardrails such as sensitivity labels and lifecycle policy to all of them.
Who configures the connection — IT or RevOps?
IT grants the initial Graph consent once. After that, sales operations or RevOps configure and adjust flows in the nFlow no-code visual builder — mapping CRM events to templates, naming, and membership rules — without raising a ticket every time the sales motion changes.
Turn every CRM event into a ready-to-work workspace.
See a Salesforce or HubSpot event provision a fully structured, governed Microsoft Teams workspace — live, in your own tenant.