Salesloft
Manage Salesloft people, accounts, cadences, cadence enrollment, calls, notes, tasks and users.
About
Salesloft ships in the w6w first-party pack. It declares 26 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.salesloft- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Communication
Overview
Salesloft brings a sales engagement platform’s core resources into a workflow — people (contacts), accounts (companies), cadences (sequences), and the calls, notes and tasks that log engagement with them. Person and account actions cover the full create/read/list/update/delete set, while cadence actions list and fetch the sequences a team runs, and cadence membership actions enroll a person into a cadence (optionally starting at a specific step) or remove them from one.
Call actions log a phone call against a person and list past calls; note actions create and list notes associated with a person or account; task actions create, list, update and delete the follow-up tasks a rep works from. User actions list and fetch the Salesloft team members (not CRM contacts) a workflow needs to assign work to.
This is a focused surface on Salesloft’s most-used v2 API resources — the generic activity-logging endpoint (which needs Salesloft-internal action/task ids this app does not expose), email activity sync, bulk import/export jobs, and CRM-sync configuration are deliberately left out.
Build with Salesloft
Three routes to the same 26 actions. The Workflow tab is generated from Salesloft's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Account
account-delete Delete an account. Not reversible without contacting Salesloft support. Removes all connected people from the account.
Update Account
account-update Update an existing account. "domain" must be unique on the current team.
Enroll Person in Cadence
cadence-membership-create Add a person to a cadence, optionally starting at a specific step.
Remove Person from Cadence
cadence-membership-delete Delete a cadence membership, removing the person from that cadence.
Delete Person
person-delete Delete a person. This operation is not reversible without contacting Salesloft support.
Delete Task
task-delete Delete a task. This operation is not reversible without contacting Salesloft support.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Salesloft's real ids.
{
"manifestVersion": "2",
"name": "salesloft-example",
"steps": [
{
"id": "account-get",
"uses": {
"app": "io.w6w.salesloft",
"action": "account-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Account
readaccount-get -
Create Account
performaccount-create -
List Accounts
readaccount-list -
Update Account
performaccount-update -
Get Cadence
readcadence-get
+21 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Salesloft, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Salesloft. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "account-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action account-get --payload '{"id":"<value>"}'Give an AI agent Salesloft — without giving it Salesloft's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.salesloft#account-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Salesloft connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Salesloft's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Salesloft itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Salesloft declares its own checks, so its health is a property of the app rather than something the host guesses at.
Salesloft platform status
Atlassian Statuspage rollup for status.salesloft.com, with per-component detail. Only the Salesloft Web Application and VoIP Provider components (Salesloft's own infrastructure) decide the reported state — the page also lists third-party integrations (Salesforce, Zoom, LinkedIn, …) whose own outages are reported for visibility but do not mean the Salesloft API itself is down. Unauthenticated and unsigned.
API rate-limit headroom
Requests remaining in the current per-minute cost window, read off the x-ratelimit-remaining-minute response header. Salesloft's rate limit is per-TEAM, so another integration on the same team can spend this same budget.