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.
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. |
{"enabled": "{{trigger.enabled}}","shareType": "{{trigger.shareType}}","pageSize": "{{trigger.pageSize}}"}
{"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.
Any of these apps can fire this action as part of a workflow.