Documentation

DocsGuidesWorkflow Blueprint: Stop-On-Reply

Workflow Blueprint: Stop-On-Reply

The cold outreach sequence uses `wait_for_event` nodes with timeout branches. A reply exits immediately. If there is no reply, the workflow advances to the next template after the configured window.

Prompt

Use $cold-outreach-writer to turn this ICP, offer, and proof into a 4-touch OutreachAgent sequence with plain human subject lines, shorthand-style body copy, and stop-on-reply logic.

Node recipe

Workflow Nodes

[
  { id: "node_trigger_intro", type: "send_email", label: "Send trigger intro", templateId: "trigger-intro", nextNodeId: "node_wait_after_trigger_intro" },
  { id: "node_wait_after_trigger_intro", type: "wait_for_event", label: "Wait 3 days or reply", waitForEvent: "message.received", nextNodeId: "node_exit", timeoutMinutes: 4320, timeoutNextNodeId: "node_pain_kpi" },
  { id: "node_pain_kpi", type: "send_email", label: "Send pain or KPI follow-up", templateId: "pain-kpi", nextNodeId: "node_wait_after_pain_kpi" },
  { id: "node_wait_after_pain_kpi", type: "wait_for_event", label: "Wait 7 days or reply", waitForEvent: "message.received", nextNodeId: "node_exit", timeoutMinutes: 10080, timeoutNextNodeId: "node_different_angle" },
  { id: "node_different_angle", type: "send_email", label: "Send different-angle follow-up", templateId: "different-angle", nextNodeId: "node_wait_after_different_angle" },
  { id: "node_wait_after_different_angle", type: "wait_for_event", label: "Wait 7 days or reply", waitForEvent: "message.received", nextNodeId: "node_exit", timeoutMinutes: 10080, timeoutNextNodeId: "node_breakup" },
  { id: "node_breakup", type: "send_email", label: "Send breakup email", templateId: "breakup", nextNodeId: "node_exit" },
  { id: "node_exit", type: "exit", label: "Exit workflow", nextNodeId: null }
]

Send gaps

wait 3 days after trigger-intro
wait 7 days after pain-kpi
wait 7 days after different-angle

Timeout-driven follow-ups require the Temporal-backed runtime. In local or preview mode, reply-based waits still work, but timed timeout branches are surfaced as workflow guidance rather than executed scheduling.