- Integrations
- /
- Outreach
- /
- Actions
- /
- List Outreach Sequences
OActionOutreachUpdated May 2026
What Outreach sequences exist?
Short answer: Drop the "Outreach → List Outreach Sequences" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Enabled Only enabled | options | Optional | Filter by sequence enabled flag. |
Share Type shareType | options | Optional | Filter by sharing visibility. |
Page Size pageSize | number | Optional | Results per page, 1–100. |
Sample request
{"enabled": "{{trigger.enabled}}","shareType": "{{trigger.shareType}}","pageSize": "{{trigger.pageSize}}"}
Returns
{"data": [{"id": "98765","type": "sequence","attributes": {"name": "Q2 Outbound — Enterprise","enabled": true,"createdAt": "2026-01-10T10:00:00.000Z","shareType": "shared","sequenceStepCount": 8}}],"meta": {"count": 1}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Outreach Sequences.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Outreach Sequences.
What does the List Outreach Sequences action do in Outreach?
Returns sequence catalog with status and prospect counts. Useful for resolving sequence IDs at workflow setup and for reporting on sequence inventory.
What inputs does List Outreach Sequences require?
List Outreach Sequences has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Outreach Sequences support batch operations?
Yes. Run List Outreach Sequences 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
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.
ActionCreate 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.
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.
Send list outreach sequences from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.