Query it the way you already think about it
Query Salesforce your way, and write the answers back
Write the query, or start from a report your team already trusts. Nexadata pulls either into a dataset, joins it to the rest of your stack, and writes results back with the action you choose.
At a glance
Two-way connectorOut of Salesforce
- SOQL, built for you or hand-written
- Saved Salesforce reports
- Standard and custom objects
Back into Salesforce
- Insert
- Update
- Upsert
- Delete
Authentication
OAuth 2.0, against production or a sandbox.
- SOC 2 Type II
- Zero data retention
- SSO / SAML / RBAC
- Cloud-agnostic
The platform processes your data. An LLM never touches it.
The connector
What the Salesforce connector does
Two ways in, depending on who is asking
Pick an object and the properties you want and Nexadata builds the SOQL for you, or open the editor and write it yourself when you need precision. When the reporting team has already agreed what the numbers mean, start from a saved Salesforce report instead and inherit their filters and aggregation.
Built for the volumes that break exports
Choose real-time extraction for freshness or high-volume mode when the record count is the problem, and set the batch size to match. Soft-deleted records are included or excluded as you decide, rather than silently one or the other.
Write back with the action you actually want
Insert, update, upsert or delete, chosen per output rather than assumed. Each pipeline column maps to a Salesforce property, and the mapping is validated against the object schema before anything is written.
Sandbox first, production when you are ready
The connection targets a production instance or a sandbox, so the same workflow can be proved against test data and then pointed at the real thing. The API version is yours to pin rather than something that moves underneath you.
Describe the extract instead of writing it
Where SOQL is the thing standing between a question and an answer, Nexadata's MCP server removes it. Claude, ChatGPT or any MCP-capable client can stand up the whole job in conversation: the workflow, the Salesforce datasets behind it, the pipelines and mappings, and the run. The reasoning happens over object and field metadata, never over the records themselves.
Sources
Connect what feeds it
Salesforce is rarely the only system in the answer. Join it to whatever else the question needs: if a system has an OpenAPI or OData spec, the Connector Copilot reads it and builds a working connection, with no prebuilt connector to wait on.
How it works
From source system to Salesforce
Connect, transform, map, review. Each step is guided by a no-code copilot, and you approve the plan before anything runs.
- 01
Connect
Authenticate through Salesforce OAuth against production or a sandbox, pin your API version, and let Nexadata handle token refresh from there.
- 02
Transform
Roll opportunity lines up to the grain your model works in, reconcile them against billing and product data, and reshape the result by describing it to the Transform Copilot.
- 03
Map
Line opportunity stages, record types and product lines up with the members your target model already uses, including the conditional cases a lookup table cannot express.
- 04
Review
Approve the plan before it runs, and keep the record of who changed a mapping group, what changed, how and when.
Use cases
What people run through it
Land pipeline in your planning model
Move opportunity and stage data into the model your forecast runs on, with the mapping from CRM stages to model dimensions held where the business can read and change it.
See the use caseStart from a report people already trust
When finance and sales have agreed what a report means, build the dataset from that report rather than rebuilding the logic in a query and inviting a second version of the truth.
Read the guideReconcile CRM against billing
Join opportunities to invoices and subscriptions from your finance systems, find what does not agree, and write the corrected view back where the team will see it.
See the use caseSet it up
Step-by-step documentation
Every screen, in order, with screenshots.
Setting up a Salesforce connection
OAuth, production or sandbox, and pinning your API version.
Read the guideUsing a Salesforce connection
Build a dataset from SOQL or a report, then write results back.
Read the guideTroubleshooting the Salesforce connector
SOQL problems, report issues and sync failures.
Read the guideConnector Copilot
For the systems around Salesforce that have no prebuilt connector.
Read the guideQuestions
Salesforce integration FAQ
- Can I write my own SOQL, or does Nexadata generate it?
- Both. Choose an object and the properties you want and the SOQL is built for you as you go, or open the query editor and write it yourself when you need something the builder will not express.
- Can I build a dataset from a Salesforce report?
- Yes. If a saved report already carries the filters and aggregation your team has agreed on, point the dataset at that report instead of rebuilding the same logic in a query and ending up with two versions of the number.
- How does Nexadata handle large Salesforce extracts?
- Pick real-time mode when freshness matters and high-volume mode when the record count is the problem, then set the record batch size to suit. You also choose whether soft-deleted records are included.
- How does Nexadata write data back into Salesforce?
- Insert, update, upsert or delete, chosen per output rather than assumed. Each pipeline column is mapped to a Salesforce property and validated against the object schema before the write runs.
- Can I test against a sandbox before touching production?
- Yes. The connection targets either a production instance or a sandbox, so a workflow can be proved against test data and then repointed. The API version is pinned by you rather than moving on its own.
More integrations
Other ways to connect
Pigment
Read from and write to Pigment blocks, views and lists, with column validation on every writeback.
ExploreAnaplan
Reach past your models into Anaplan's own tenant data, and load results back through the actions your model already runs.
ExploreHubSpot
Read any standard or custom object with its associations, and write results back with upsert, create or update.
ExploreConnector Copilot
Load a spec, authenticate, describe the data you want, and get a typed dataset. Over 20,000 public APIs are documented in OpenAPI.
ExplorePDF documents
Detect and curate the tables inside a document, then reuse that configuration on every later file in the same layout.
ExploreSpreadsheets
Point at the sheet and the cell where the real data starts, and load a clean typed table out of a messy workbook.
ExploreSee it on your data
Start free with your first use case, or talk to us about your stack.