CRM & Sales · Integration
Salesforce
Add Salesforce to your product for your customers, and give your AI agents governed access to it.
Salesforce is the CRM most of your customers already run, so an embedded Salesforce integration decides whether onboarding one of them is configuration or a services project. Reads and writes cover accounts, contacts, leads, opportunities and cases, plus the custom objects, record types and picklists an org has grown around them, with SOQL for anything a list endpoint cannot express. Three facts shape the build. No two orgs share a schema, so discovering fields at connect time beats a mapping compiled into your code. Request allowance is counted per org across a rolling day and shared with every other tool that customer has connected, so an unthrottled backfill becomes somebody else's outage. And a sandbox is not production. fastn holds each org's credentials, refreshes tokens and absorbs the release changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer authorise their own Salesforce org, then read their field and record type metadata at connect time so an unusual schema is setup rather than engineering.
Write leads, contacts and opportunities into the record types and picklist values that org actually uses, instead of defaults you chose.
Use Bulk for volume and single calls for the rest, so a first import does not consume the allowance the customer's other tools depend on.
Subscribe to record change events so a stage move or a closed case advances your workflow while it still matters.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads an account with its open opportunities and recent cases before answering a renewal question.
An agent updates an opportunity or logs an activity under the permissions the connected user holds, and the call is recorded.
An agent composes SOQL against the fields that org genuinely has rather than the standard ones it expected.
Example prompt
Which opportunities on this account went closed-lost last quarter, and does any case explain why?
Set up Salesforce in 4 steps
- 01Open the Salesforce connector from your fastn dashboard.
- 02Have each customer authenticate their Salesforce org with OAuth.
- 03Map the objects and fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Salesforce integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Salesforce integration without building it. Your customers connect their own Salesforce 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 update is not your on-call problem.
- One integration serves your product and your agents. The same governed Salesforce 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
HubSpot
Microsoft Dynamics
Salesforce Data CloudOften used alongside
Tools the same teams tend to run next to Salesforce, across other categories.
Slack
Mailchimp
Marketo
Google AdsSalesforce integration FAQ
How do I add a Salesforce integration to my product?
Enable the Salesforce connector in your fastn dashboard, then let each customer authenticate their own Salesforce account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Salesforce 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 account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Salesforce 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 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 an account with its open opportunities and recent cases before answering a renewal question.
Who maintains the Salesforce integration?
fastn does. When Salesforce 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 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 schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Salesforce, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Salesforce do not drift apart.
What can I build with the Salesforce integration?
A common starting point: let each customer authorise their own Salesforce org, then read their field and record type metadata at connect time so an unusual schema is setup rather than engineering. 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 integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Salesforce does not change your per-connector cost. You can start free with 3 connected accounts.
Add Salesforce to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.