ActionOutreachUpdated September 2026
How do I enroll a prospect in an Outreach sequence?
Short answer: You can add prospect to sequence in Outreach by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Outreach Add Prospect to Sequence action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Prospect ID prospectId | string | Required | The Outreach prospect ID to enroll. |
Sequence ID sequenceId | string | Required | The sequence to enroll the prospect into. |
Mailbox ID mailboxId | string | Required | The mailbox (sender) the sequence will send emails from. |
Sample request
{"prospectId": "1234567","sequenceId": "98765","mailboxId": "11"}
Returns
{"data": {"id": "555666","type": "sequenceState","attributes": {"state": "active","createdAt": "2026-04-11T10:00:00.000Z"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Add Prospect to Sequence.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Add Prospect to Sequence.
What does the Add Prospect to Sequence action do in Outreach?
Enrolls a prospect with optional mailbox override. For "qualified lead → start nurture" or "trial signed up → enroll in activation sequence" workflows.
What inputs does Add Prospect to Sequence require?
Required: Prospect ID, Sequence ID, Mailbox 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 Add Prospect to Sequence support batch operations?
Run Add Prospect to 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
Other Outreach actions.
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.
ActionList Outreach Sequences
Returns sequence catalog with status and prospect counts. Useful for resolving sequence IDs at workflow setup and for reporting on sequence inventory.
ActionRemove Prospect from Sequence
Stops a prospect's enrollment in a sequence. Common pattern: prospect replied → remove from competing sequences to prevent double-touching.
ActionUpsert 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.