Claude Salesloft connectorWhat Claude can do in your Salesloft account.
The Claude Salesloft connector exposes 14 tools. 9 read your accounts, deals, contacts and calls, 0 are documented as writing, and 5 are described nowhere. Below: what Claude can answer, what it cannot touch, and who controls access.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach Salesloft
Salesloft holds the history of your deals: accounts, contacts, calls and their transcripts. With the connector, you ask Claude a question about your pipeline or a customer, and it answers from live Salesloft data instead of a stale export. Everything documented here is reading: the directory sheet describes asking questions, not changing records.
Walk into a call prepared. account_by_id and person_by_id bring a customer's live record into the chat, so Claude can sum up who you are dealing with and what happened lately.
Hear what buyers actually said. search_conversations and conversation_transcript_by_id let Claude answer from real call content, quoting an objection instead of guessing it.
Check the pipeline without a report. search_opportunities answers questions about deal status and activity across what you own.
What the connector does not do, as documented: it writes nothing. No listed tool is described as updating a deal, logging a call or sending an email, and the sheet frames everything as questions. Keep in mind this is a floor, not a promise: an administrator can open actions that appear on no public sheet. Nothing runs by itself either. If you want deal changes pushed to other tools on a schedule, that is an automation job, a different one, covered on our Salesloft Make integration page.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude chooses the tools it needs by itself, and the directory lists them by name.
- Authorization
- The Salesloft sign-in screen where you hand Claude the access it will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it does something that changes your account, shown in the chat at the right moment.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Salesloft.
Connect Salesloft to Claude in three steps
- 01
Find Salesloft in Claude
Open Claude's settings, go to Customize then Connectors, and look for Salesloft in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first; each member then signs in on their own.
- 02
Start the connection
Click Connect on the Salesloft row, then sign in to Salesloft in the window the service opens itself, not inside Claude. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Check what the screen lists before you accept. It belongs to Salesloft, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Salesloft account.
The 14 tools, split by what they do
Salesloft gives Claude 14 tools: 9 that read your account, 0 that change something in it, and 5 no official source describes.
Two groups: what Claude reads, and what no official source describes. No tool is documented as writing. Names stay as Claude shows them.
- 9 read
- 5 not documented
What Claude can read in Salesloft
9 toolsNine tools covered by the directory sheet's description: questions about deals, accounts, contacts and calls.
account_by_id
Brings one account's live Salesloft data into the chat, so Claude answers about that customer from real engagement and deal activity rather than memory.
conversation_by_id
Opens a single recorded conversation from Salesloft so Claude can tell you what was discussed and with whom, grounded in the real exchange.
conversation_transcript_by_id
Gives Claude the transcript of a Salesloft call, the actual words exchanged, so it can quote objections or pull out next steps.
opportunity_by_id
Pulls one deal's live record from Salesloft, so Claude can report where it stands and what activity sits behind it.
person_by_id
Shows what Salesloft holds on one contact, including the engagement recorded with them, so Claude can prepare you for the next touchpoint.
search_accounts
Lets Claude look across your accounts in Salesloft to answer a question that spans several customers at once.
search_conversations
Finds conversations across your Salesloft data, so Claude can answer questions about calls without you knowing which one to open.
search_opportunities
Looks through your deals in Salesloft, which lets Claude answer pipeline questions grounded in live data.
search_people
Searches the contacts you can see in Salesloft so Claude can find the right person before answering.
Not documented
5 toolsFive names the directory publishes with no description. Undocumented means exactly that: no source says what they do.
conversation_recording_by_id
This name appears in the directory's tool list and nowhere else. Neither Salesloft's documentation nor any Claude page describes it, so this page says nothing more about it. Treat any answer that leans on it with care until a source documents it.
current_team
Listed by name on the directory sheet, with no official sentence behind it. We do not guess its role from its name, even when the name looks obvious, because that is how wrong pages get written.
current_user
No official text, from Salesloft or from Anthropic, explains this entry. The directory publishes the name and stops there, with no example, no field and no side effect described.
search_users
Only the name is public. The documentation we read does not mention it, and reading a purpose into a name would be guessing, which this page refuses to do for any tool.
user_by_id
Nothing official describes this one beyond its presence in the directory's list. This page leaves it at that on purpose, rather than fill the gap with a plausible story.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. With only reads documented, the question rarely comes up here.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, for example leaving reads open and closing writes. Nobody overrides that from a personal account. Claude also works with the rights of the person who connected, nothing more: Salesloft's sheet says role-scoped permissions mean you only see your own data.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, check the Salesloft sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a deal moves or a call ends.
This page rests on the directory sheet alone: no Claude help page covers Salesloft, and the publisher's own help article could not be read for it. The badge in the directory is not a security audit, and Anthropic says on each sheet that it neither picks a publisher's tools nor guarantees their behavior. A connected community tool would have exactly the same access, so the publisher matters more than the badge. For other sales apps, see our Integrations hub.
Need help connecting Salesloft to Claude?
A person reads every message.
