Skip to main content

Import Salesforce CRM accounts

Quick start​

Connect Salesforce CRM in NEXT, enable the Teamspace subscription for this import, and let the scheduled sync pull Salesforce accounts and opportunities into NEXT as Accounts. If you use NEXT automations, the same integration can also create Salesforce Tasks linked to the correct account.

Why integrate with Salesforce CRM?​

Salesforce is the system of record for many revenue organizations. Pulling CRM context into NEXT means customer intelligence can be interpreted through the lens of account value, segment, ownership, and pipeline instead of living as disconnected notes.

  • It ties product demand and customer pain directly to CRM accounts.
  • It helps teams prioritize insights by ARR, stage, or segment rather than anecdote.
  • It gives downstream workflows a reliable account context for routing, automation, and reporting.
  • It lets NEXT automations create Salesforce Tasks so follow-up work lands where GTM teams already operate.

What the integration does​

Account import​

  • Object in NEXT: Accounts
  • Source objects: Salesforce accounts and opportunities
  • Included fields: Account name, industry, billing region, employee size bracket, account type, opportunity stage, and ARR when available.

Automation write-back​

  • Object in Salesforce: Tasks
  • Trigger: NEXT automations that create follow-up actions in Salesforce
  • Behavior: Tasks are linked to the correct Salesforce Account so summaries and follow-ups stay attached to the existing CRM record

What gets imported​

  • Object in NEXT: Accounts
  • Source objects: Salesforce accounts and opportunities
  • Included fields: Account name, industry, billing region, employee size bracket, account type, opportunity stage, and ARR when available.

Authentication​

Client credentials configured for the Salesforce connected app used by NEXT.

Connection notes​

  • Configure the Salesforce CRM integration with the instance URL, consumer key, and consumer secret.
  • Enable the Teamspace subscription that should receive account updates from Salesforce.

Configuration notes​

  • Only changed accounts and opportunities are fetched on each sync.
  • NEXT combines account and opportunity data so imported accounts carry pipeline context.
  • Manual reruns follow the same delta logic unless you explicitly backfill from an earlier point.

Limitations​

  • This sync does not create Salesforce records; it only reads from Salesforce into NEXT.
  • Permissions on the integration user determine which account data can be imported.
  • The only Salesforce write-back covered by this integration is Task creation through NEXT automations.

Troubleshooting​

  • Verify the connected app still allows the client credentials flow and that the secret has not rotated.
  • If syncs stop unexpectedly, check whether the integration user still has read access to the relevant objects.
  • If Salesforce Task creation fails, confirm the integration user has Create permission on Tasks and is authorized for the Connected App.
  • If authentication fails, verify the instance URL matches the correct Salesforce org and the Connected App still has client credentials enabled.
  • If imports slow down or fail during heavy reruns, check whether your Salesforce org is near its API request limits.

FAQ​

Does NEXT sync opportunities separately?​

NEXT reads opportunity data to enrich imported accounts, but the user-facing result is an Account sync.

Can I run a backfill?​

Yes. Adjust the subscription start point or trigger a rerun so NEXT reads older changed records again.

Does the integration write back to Salesforce?​

It does not modify Accounts or Opportunities. The only write-back is Salesforce Task creation from NEXT automations when that workflow is enabled.

How often does the sync run?​

The import runs on a scheduled cadence and processes records changed since the previous successful run.

What permissions does the integration user need?​

The integration user needs API access plus read access to Accounts and Opportunities. If you want automation-created Tasks, that user also needs Create permission on Tasks.