Start free
ActionOutreachUpdated June 2026

How do I remove a prospect from a sequence?

Short answer: You can remove prospect from sequence in Outreach by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Outreach Remove Prospect from Sequence 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.

Remove Prospect from Sequence in Outreach — start free All 5 Outreach actions
Remove Prospect from Sequence in Outreach — 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
Sequence State ID
sequenceStateId
stringRequiredThe sequenceState ID returned when the prospect was enrolled.
Sample request
{
  "sequenceStateId": "555666"
}
Returns
{
  "removed": true,
  "sequenceStateId": "555666"
}

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

Triggered by

Apps that pair well as the trigger for Remove Prospect from Sequence.

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

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

Questions about Remove Prospect from Sequence.

What does the Remove Prospect from Sequence action do in Outreach?
Stops a prospect's enrollment in a sequence. Common pattern: prospect replied → remove from competing sequences to prevent double-touching.
What inputs does Remove Prospect from Sequence require?
Required: Sequence State 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 Outreach 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 Remove Prospect from Sequence support batch operations?
Yes. Run Remove Prospect from Sequence inside a Loop node to process arrays. TinyCommand handles Outreach's rate limits automatically so you don't have to throttle manually.
More actions

Other Outreach actions.

Action
Add Prospect to Sequence
Enrolls a prospect with optional mailbox override. For "qualified lead → start nurture" or "trial signed up → enroll in activation sequence" workflows.
Action
Create Outreach Task
Creates a follow-up task for a rep (e.g., post-meeting call). For "demo completed → create the proposal-follow-up task" workflows.
Action
List Outreach Sequences
Returns sequence catalog with status and prospect counts. Useful for resolving sequence IDs at workflow setup and for reporting on sequence inventory.
Action
Upsert Outreach Prospect
Match by primary email — create or update in one call. The base hook for "CRM contact → push to Outreach for outbound activity" sync workflows.
Remove Prospect from Sequence in Outreach — start free