nFlow

Bring Salesforce into the flow of Microsoft Teams—automatically. nFlow creates the right

Team, channel, or chat from Opportunity, Account, Case, or any Custom

Object activity, pins the record as a tab, posts live highlights, and keeps people, naming, and lifecycle aligned

with your process.

What nFlow does

• Deal & case rooms: Auto-create a Team/channel per opportunity or case; pin the record; trigger stage checklists; auto-archive on Closed Won/Lost or Resolved.
• Account workspaces: Structured Teams with ready-made channels, tabs, folders, and starter content.
• Record-driven spaces: Rule-based creation from any Salesforce object/field (stage, amount, owner, region, type, etc.).
• Record ↔ space linking: Detect and reuse existing rooms to prevent duplicates.
• Live highlights & nudges: Post stage changes and key field updates as adaptive cards; @mention the right people.
• Templates: Apply Team/Channel templates with tabs (Planner, Files, OneNote, Lists, Power BI), folder structures, task boards, and documents.
• Membership sync: Mirror Account or Opportunity team members; auto-add SMEs based on rules.
• Lifecycle by design: Sensitivity labels, naming conventions, approval flows, retention, and timed archive—applied automatically.

Works for Salesforce and non-Salesforce users

Salesforce users get the record in a tab and actionable updates in Teams. Colleagues without Salesforce licenses collaborate

in the same channels and chats—files, tasks, and decisions stay in Teams while nFlow keeps the record and workspace in sync.

Security & compliance

• Least-privilege access to Microsoft Graph and Salesforce via OAuth.
• Encryption in transit and at rest; audit logging and admin health checks.
• Enterprise compliance: sensitivity labels, retention policies, DLP, lifecycle guardrails applied by template.
• Attestations: ISO 27001 certificate; SOC 2 Type II report available under NDA.

Requirements

• Microsoft 365 tenant with Teams enabled and admin consent.
• Salesforce org (sandbox and/or prod) connected via OAuth.

Why teams choose nFlow

• Less app-switching: updates surface where collaboration happens.
• Consistent execution: stage-based checklists and templates built into every space.
• Scales with structure: policy-driven naming, membership, and lifecycle.

Get started

• Install: Add nFlow in Microsoft Teams and request admin consent if required.
• Connect: Sign in with your Salesforce org and choose your templates.