CRM & Sales · Integration
Salesforce Data Cloud
Add Salesforce Data Cloud to your product for your customers, and give your AI agents governed access to it.
Embed a Salesforce Data Cloud integration so your customers can bring their unified profiles, segments, and calculated insights into your product, and so your AI agents can read that context under per-tenant governance. fastn handles each customer's OAuth grant, data space scoping, and API upkeep, so you support the long tail of Data Cloud configurations without writing a per-customer integration.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers pull unified individual and account profiles into your product, mapped to their own data model.
Read segment membership so your product can personalise behaviour per end user.
Trigger your product when a customer's segment membership or calculated insight changes.
Support each customer's own data spaces and object mappings without shipping code per customer.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a unified customer profile before answering, instead of guessing from stale local data.
An agent checks segment membership to decide which action is appropriate for a given customer.
An agent reacts to a change in a calculated insight and runs the next step of a workflow.
Example prompt
Look up this account's unified profile in Data Cloud, list the segments it belongs to, and flag any with a churn-risk insight above threshold.
Set up Salesforce Data Cloud in 4 steps
- 01Open the Salesforce Data Cloud connector from your fastn dashboard.
- 02Have each customer authenticate their Salesforce org with OAuth and grant Data Cloud access.
- 03Map the profile objects, segments, and insights your product uses, then enable the actions and triggers you need.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Salesforce Data Cloud integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Salesforce Data Cloud integration without building it. Your customers connect their own Salesforce Data Cloud account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Salesforce Data Cloud update is not your on-call problem.
- One integration serves your product and your agents. The same governed Salesforce Data Cloud connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
SalesforceWorks well with
Snowflake
SlackOften used alongside
Tools the same teams tend to run next to Salesforce Data Cloud, across other categories.
Mailchimp
Marketo
Google Ads
Microsoft TeamsSalesforce Data Cloud integration FAQ
How do I add a Salesforce Data Cloud integration to my product?
Enable the Salesforce Data Cloud connector in your fastn dashboard, then let each customer authenticate their own Salesforce Data Cloud account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Salesforce Data Cloud client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Salesforce Data Cloud account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Salesforce Data Cloud account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Salesforce Data Cloud integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a unified customer profile before answering, instead of guessing from stale local data.
Who maintains the Salesforce Data Cloud integration?
fastn does. When Salesforce Data Cloud changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Salesforce Data Cloud integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Salesforce Data Cloud schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Salesforce Data Cloud, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Salesforce Data Cloud do not drift apart.
What can I build with the Salesforce Data Cloud integration?
A common starting point: pull unified individual and account profiles into your product, mapped to their own data model. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Salesforce Data Cloud integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Salesforce Data Cloud does not change your per-connector cost. You can start free with 3 connected accounts.
Add Salesforce Data Cloud to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.