Outreach
Outreach sequence and prospect events
Outreach is the sales-engagement platform that runs outbound and post-meeting sequences for SDR teams, and Tiny Command surfaces two high-value triggers: Prospect Replied (a prospect responded to any sequenced email — the moment that pulls them out of automation and into a human handoff) and Sequence Step Finished (a step completed, which is the granular hook for per-touch analytics). Five actions handle the prospect lifecycle: Upsert Prospect (match by email; create or update in one call, the standard sync action), Add Prospect to Sequence (enroll with optional mailbox override), Remove Prospect from Sequence, Create Task (e.g., a follow-up call after a meeting), and List Sequences (for dynamic dropdowns and reporting). Prospect Replied is the workflow trigger for stopping competing automation — common pattern: when fired, remove the prospect from every other sequence to prevent double-touching. The mailbox concept matters: a sequence can be sent from any rep's mailbox; the trigger payload tells you which.
Workflows start when Outreach does.
2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a prospect responds to a sequenced email — the moment that pulls them out of automation. For "remove from competing sequences, notify the AE, log to CRM" hand-off workflows.
Fires per-step as sequences progress. For granular activity-tracking workflows that need to log each touch separately.
Do anything Outreach can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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. |
| 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. |
| List Outreach Sequences | Returns sequence catalog with status and prospect counts. Useful for resolving sequence IDs at workflow setup and for reporting on sequence inventory. |
| Remove Prospect from Sequence | Stops a prospect's enrollment in a sequence. Common pattern: prospect replied → remove from competing sequences to prevent double-touching. |
| Upsert 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. |
Pre-built Outreach workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Outreach once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Outreach field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Outreach integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Outreach to Tiny Command?
What Outreach triggers does Tiny Command support?
What Outreach actions can I run from a workflow?
Is the Outreach integration real-time?
Do I need to write code to use Outreach with Tiny Command?
How much does the Outreach integration cost?
More email apps people connect.
Same category as Outreach, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Outreach.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
