Salesloft Remove from Cadence: Salesloft action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Cadence Membership ID membership_id	string	Required	The 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.

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. Tiny Command handles Salesloft's rate limits automatically so you don't have to throttle manually.

More actions