ActionOutreachUpdated September 2026

What Outreach sequences exist?

Short answer: You can list outreach sequences in Outreach by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Outreach List Outreach Sequences 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.

List Outreach Sequences in Outreach — start free All 5 Outreach actions

List Outreach Sequences 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
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.

Google Sheets → Outreach

2 Google Sheets triggers

HubSpot → Outreach

18 HubSpot triggers

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 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 List Outreach Sequences support batch operations?

Run List Outreach Sequences 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