StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Salesloft cadence provider contract.

1 listed action1 capability groups

Connection facts

What the Salesloft connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
oauth-or-api-key
Setup
Register a Salesloft OAuth app with the fixed StackOS callback and cadences:write scope, then use Connect with Salesloft. Customer API keys remain an explicit supported alternative.
Capability groups
Outbound Operations
Action boundaries
1 write action

Action catalog

Actions listed for Salesloft.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

1 matching action

Outbound OperationsCan make changes

Create Salesloft Cadence Membership

Add an explicit person to a Salesloft cadence after approval.

Direct answer

How does the Salesloft integration work?

People continue using Salesloft as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03SalesloftDoes its bounded part
  4. 04Checked resultKeeps the proof

More from GTM And RevOps

Related integrations.

See the plugin →

Common questions

Salesloft and StackOS.

What can the Salesloft integration do in StackOS?

The current catalog includes 1 Salesloft action across Outbound Operations. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Salesloft?

No. Salesloft remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.