1. Integration Method

Inventive's Salesforce integration works in two directions, each with a clear purpose:

• Salesforce → Inventive — bring an Opportunity into Inventive. When someone opens an Opportunity, the embedded Inventive widget reads its fields as the signed-in user (so it only ever shows what that person can already see) and uses them to pre-fill a project form that the user reviews and submits to create the linked Inventive project. Those fields are sent to Inventive over a Salesforce Named Credential — a secure channel that proves which org is calling but has no standing access to your Salesforce data of its own.
• Inventive → Salesforce — push finished documents back. When someone exports a finished document, Inventive writes it back onto that same Opportunity through the Salesforce REST API, over a connection an admin authorizes once on Salesforce's standard consent screen (set up via Nango OAuth Broker). Every call runs as that authorized Salesforce user.

Either way, what can be read or changed is governed by Salesforce's own permissions — never a generic Inventive login (see Access Control below). Both directions use OAuth 2.0; they differ only in the OAuth flow each uses — client-credentials (machine-to-machine) for the widget, authorization-code (admin consent) for the connection.

2. Integration Architecture

The integration is made up of two independent workflows, one per direction. Each has a one-time Setup and a live flow for everyday use.

Workflow A — Salesforce → Inventive (pull the Opportunity into Inventive)

This is how an Opportunity is pulled into Inventive — the embedded widget reads the record so a user can create an Inventive project for that deal.

Authenticated by the Named Credential — OAuth 2.0 client-credentials (machine-to-machine).

%%{init: {'theme':'base','themeVariables':{'actorBkg':'#2563EB','actorBorder':'#1d4ed8','actorTextColor':'#ffffff','actorLineColor':'#94a3b8','signalColor':'#475569','signalTextColor':'#0f172a','noteBkgColor':'#f8fafc','noteTextColor':'#0f172a','noteBorderColor':'#cbd5e1'}}}%%
sequenceDiagram
    actor U as User / Admin
    participant W as Inventive Widget (in Salesforce)
    participant LDS as Lightning Data Service
    participant NC as Named Credential
    participant INV as Inventive Platform

    rect rgb(223, 240, 216)
    note over U,INV: 1. Setup (one-time, admin)
    U->>NC: Install managed package (creates Named Credential)
    U->>INV: Generate credentials (admin, in Inventive settings)
    INV-->>U: Return Client ID and Secret (secret shown once)
    U->>NC: Paste Client ID and Secret into External Credential
    end

    rect rgb(214, 232, 250)
    note over U,INV: 2. Create the project (user action)
    U->>W: Open the Opportunity (widget loads)
    W->>LDS: Request the record's fields
    LDS-->>W: Return fields (as signed-in user, FLS and sharing enforced)
    note over W: Widget pre-fills the project form from these fields
    U->>W: Review details, add team members, then Submit
    W->>NC: Send the new project's data
    NC->>INV: Authenticated callout (bearer token injected)
    INV-->>W: Project created and linked to the Opportunity
    end

    rect rgb(255, 235, 205)
    note over U,INV: 3. Sync later changes
    U->>W: Reopen the Opportunity
    W->>LDS: Read current fields
    LDS-->>W: Return fields
    note over W: Widget compares against saved project and flags changes
    U->>W: Click Sync Changes
    W->>NC: Send updated fields
    NC->>INV: Authenticated callout
    INV-->>W: Project updated
    end

• Setup (one-time, admin): Install the Inventive managed package — this creates the Named Credential automatically — then copy the Client ID & Secret issued in the Inventive App (Settings → Integrations, admin only) into Setup → Named Credentials → External Credentials → Inventive.
• Create a project (user action): A user opens an Opportunity; the widget pre-fills a form from the record, and they review it, add team members, and click Submit to create the linked Inventive project. Nothing is created automatically.
• Sync later changes (user action): On a later visit, if the Opportunity has changed, the widget flags it and the user can click "Sync Changes" to update a subset of fields (name, amount, close date, account name/description, and creator/owner info).
• How data is read & sent: All reads run through Lightning Data Service as the signed-in user (honoring their FLS, object permissions, and sharing); data reaches Inventive through the Apex → Named Credential callout, with the bearer token injected by the platform and never seen by the widget or Apex code. There's no background or scheduled sync — every create and update is a deliberate user action.

Workflow B — Inventive → Salesforce (push documents back to the Opportunity)

This is the connection Inventive uses to push the documents you generate back onto the Salesforce Opportunity that was synced in via Workflow A.