Add Prospect to Sequence: Outreach 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
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.

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 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 Add Prospect to Sequence support batch operations?

Yes. Run Add Prospect to Sequence inside a Loop node to process arrays. Tiny Command handles Outreach's rate limits automatically so you don't have to throttle manually.

More actions