ActionOutreachUpdated September 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.

Field	Type	Required	Description
Sequence State ID sequenceStateId	string	Required	The 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.

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 run history shows the failed step with its input and the error message Outreach returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Remove Prospect from Sequence support batch operations?

Run Remove Prospect from Sequence inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Outreach's rate limits.

More actions