What connects

The connection uses Salesforce's OAuth web flow through a server-configured Connected App. The requested OAuth scope is api refresh_token so the server can read the connected org and keep scheduled syncs working.

An IntellaOne administrator configures the server-side Connected App client credentials and callback URL.
The customer Salesforce administrator or connected user approves the OAuth request and must grant the Salesforce API and account, contact, opportunity, and activity permissions being requested.

Information used

Inbound sync reads the normalized CRM fields that IntellaOne uses for account-aware guidance. The connection keeps a LastModifiedDate watermark for each object so later runs look for changes instead of treating the newest records as a complete history.

Accounts: name, industry, employee count, annual revenue, and website.
Contacts: name, email, title, department, phone, and account relationship.
Opportunities: name, stage, amount, close date, probability, closed/won state, owner, and account relationship.
Accounts, contacts, and opportunities can each be disabled in the connection's inbound sync settings.

Why it is useful

The synced records give a seller the account and opportunity context behind a live conversation without requiring a CRM tab switch. Contact and opportunity links can also identify the intended records for a post-call outcome.

How the workflow behaves

Salesforce data refreshes automatically on the provider's 15-minute cadence. A rep can review a proposed outcome and approve it, or explicitly forward notes; this is not an automatic arbitrary-field import.

The outbound action is one completed Salesforce Task/Call containing the subject, summary, and optional next steps.
The activity may include an optional contact and opportunity link when those records have been resolved.
The connection's outbound activity toggle can turn this write-back off.
IntellaOne does not update arbitrary Salesforce fields, import products, or claim to import a Salesforce activity history through this connection.

Prerequisites and limits

Before connecting, an IntellaOne administrator must configure the server-side Salesforce Connected App, callback, and client credentials. The customer Salesforce administrator or connected user must then authorize the OAuth request and grant org API access plus the required user/object permissions. Provider limits, authorization expiry, and org API request limits can interrupt a sync.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

CRM write-back requires explicit rep initiation or approval: proposal approval authorizes proposal writes, while forwarding notes occurs only after an explicit rep action.

Inbound object toggles limit which CRM objects are synced for this connection.
A successful write depends on Salesforce accepting the approved action; provider behavior can change.