Skip to content
NexusBook a demo

Enterprise use case · HubSpot + Salesforce + Microsoft 365

Marketing to sales handoff

Leads wait in marketing tools, arrive duplicated and reach the wrong owner. Qualified leads reach the right salesperson fast, with duplicates caught.

Systems involved

What each system contributes

HubSpot

69 actions

  • Contacts15
  • Deals10
  • Forms10
Salesforce

73 actions

  • Leads10
  • Contacts10
  • Opportunities10

Trigger source: Salesforce (SOQL polling)

Microsoft 365

45 actions

  • Teams16
  • Emails14

Trigger source: Microsoft Teams

Architecture

One governed run

Trigger: webhook / scheduleIntegration: HubSpot + SalesforceRules + CodeHuman ApprovalSystem Action: SalesforceAudit

How it starts: A webhook, HTTP poll or schedule starts the run.

Step by step

How the process runs

  1. 01

    Lead

    HubSpot contacts, deals and forms are read.

  2. 02

    Dedupe

    Rules + Code matches Salesforce records.

  3. 03

    Create

    Salesforce leads, contacts or opportunities update.

  4. 04

    Notify

    The owner is told in Teams or email.

Control

Human decision and exception path

Human decision

Sales operations reviews ambiguous matches.

Exception path

  • Missing fields route to correction.
  • Validation failures are captured.
  • Rate limits are retried.

Evidence

What gets audited

  • Lead data.
  • Match decision.
  • Salesforce record.
  • Notification.

Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.

Sovereignty and deployment

Related

Patterns, connectors and next steps

FAQ

Questions about this use case

Does Nexus replace any of these systems?
No. Each system keeps its own records. Nexus runs the process between them and records each decision.
How does the run start?
A webhook, HTTP poll or schedule starts the run.
What if a step is not covered by a pre-built action?
It runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.

Use case review

Discuss this use case

Bring your version of the process. We will map the systems, approvals and evidence it needs.