Start free
ActionSalesloftUpdated June 2026

How do I remove a person from a Salesloft cadence?

Short answer: You can salesloft remove from cadence in Salesloft by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Salesloft Salesloft Remove from Cadence action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Salesloft Remove from Cadence in Salesloft — start free All 6 Salesloft actions
Salesloft Remove from Cadence in Salesloft — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Cadence Membership ID
membership_id
stringRequiredThe cadence membership ID returned when the person was enrolled.
Sample request
{
  "membership_id": "555666"
}
Returns
{
  "removed": true,
  "membership_id": "555666"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Salesloft Remove from Cadence.

Any of these apps can fire this action as part of a workflow.

Gmail → Salesloft
1 Gmail triggers
Slack → Salesloft
13 Slack triggers
Google Sheets → Salesloft
2 Google Sheets triggers
HubSpot → Salesloft
18 HubSpot triggers
FAQ

Questions about Salesloft Remove from Cadence.

What does the Salesloft Remove from Cadence action do in Salesloft?
Stops a person's enrollment in a cadence. Standard pattern: prospect replied → remove from competing cadences to prevent double-touching.
What inputs does Salesloft Remove from Cadence require?
Required: Cadence Membership ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Salesloft returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Salesloft Remove from Cadence support batch operations?
Yes. Run Salesloft Remove from Cadence inside a Loop node to process arrays. TinyCommand handles Salesloft's rate limits automatically so you don't have to throttle manually.
More actions

Other Salesloft actions.

Action
Salesloft Add Person to Cadence
Enrolls a person in a sequence. For "qualified lead → start the outbound cadence" or "trial signed up → enroll in activation sequence" workflows.
Action
List Salesloft Cadences
Returns paginated cadences with metadata. Useful for resolving cadence IDs at workflow setup.
Action
Salesloft Log Call
Records a call activity tied to a person with notes, duration, disposition. For "external dialler → log to Salesloft for unified sales-activity tracking" workflows.
Action
Salesloft Log Email
Records an email activity tied to a person. For "rep replied via Outlook directly → log to Salesloft cadence" sales-activity capture.
Action
Salesloft Upsert Person
Email-based dedupe — create or update in one call. The base hook for "external lead source → push to Salesloft for outbound activity" sync.
Salesloft Remove from Cadence in Salesloft — start free