CRM & Sales · Integration
Salesloft
Add Salesloft to your product for your customers, and give your AI agents governed access to it.
Salesloft is where a sales team runs its outbound motion, and its object model reflects that: people and accounts, cadences with ordered steps, cadence memberships, and the calls, emails and other activities logged against a person. It has cadences rather than campaigns, which is why it belongs with CRM and sales tooling rather than marketing automation, exactly as Apollo does in this catalog: the questions worth answering are about records, custom fields and two way movement, not about sends and audiences. So an embedded Salesloft integration is about keeping a person's state honest in both directions, adding someone to a cadence when your product sees a reason to, and reading the activity that came back. Custom fields are common and mapped per tenant. fastn holds the credentials, refreshes the tokens and follows the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Salesloft team so people, accounts and opportunities are readable and writable inside your product.
Add or remove a person from a cadence when something happens in your app, so outreach follows real activity rather than a list upload.
Read call and email activity per tenant so your product shows what was actually attempted against an account.
Map the custom fields a team has added to people and accounts as configuration, so an unusual setup needs no release from you.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a person's cadence history and recent activity before it drafts the next touch for a human to approve.
An agent adds a shortlist to a cadence within governed permissions, with each write attributed.
An agent reports which accounts have had no logged activity in a fortnight, reading only that customer's team.
Example prompt
Which people in this cadence have replied, and which have had no activity logged for over a week?
Set up Salesloft in 4 steps
- 01Enable the Salesloft connector in your fastn dashboard.
- 02Have each customer authorise their own Salesloft team with OAuth.
- 03Map the person, account, opportunity and custom fields your product uses, then enable the cadence actions and activity triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Salesloft integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Salesloft integration without building it. Your customers connect their own Salesloft 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 Salesloft update is not your on-call problem.
- One integration serves your product and your agents. The same governed Salesloft 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
Outreach
Apollo
SalesforceOften used alongside
Tools the same teams tend to run next to Salesloft, across other categories.
Slack
Mailchimp
Marketo
Google AdsSalesloft integration FAQ
How do I add a Salesloft integration to my product?
Enable the Salesloft connector in your fastn dashboard, then let each customer authenticate their own Salesloft account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Salesloft client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Salesloft account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Salesloft 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 Salesloft 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 person's cadence history and recent activity before it drafts the next touch for a human to approve.
Who maintains the Salesloft integration?
fastn does. When Salesloft 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 Salesloft 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 Salesloft schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Salesloft, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Salesloft do not drift apart.
What can I build with the Salesloft integration?
A common starting point: let each customer connect their own Salesloft team so people, accounts and opportunities are readable and writable inside your product. 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 Salesloft integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Salesloft does not change your per-connector cost. You can start free with 3 connected accounts.
Add Salesloft to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.