Journeys & Automations
Build multi-step email journeys with triggers, conditions, and waits. Chain journeys together and use drip scheduling to control enrollment over time.
Journeys are multi-step automated email sequences tied to a subscriber list. A subscriber enters via a trigger, then moves through steps in order — the journey engine processes one step every 5 seconds per enrollment.
Automatically enroll subscribers when they're added to the journey's list. The most common trigger for welcome series and onboarding flows.
TriggerEnroll subscribers when they generate a specific event — open, click, bounce, or complaint. Optionally filter to events from a specific campaign.
TriggerChain journeys together. When a subscriber completes one journey, they're automatically enrolled in the next. Build complex multi-phase workflows.
TriggerNo automatic trigger. Enroll subscribers individually or in bulk via the API or dashboard. Full control over who enters and when.
TriggerCombine three step types to build any automation flow you need. Steps execute in order, and the journey engine advances each enrollment through the sequence.
Send an email using a specific template and sender identity. DKIM signing, merge tags, tracking pixel, and link rewriting all apply automatically. Suppressed subscribers are silently skipped.
Pause the subscriber at this step for a configurable duration before advancing. Common durations: 1 hour, 1 day, 3 days, 7 days, 14 days, or 30 days.
Evaluate rules against subscriber data using the same operators as segments. If all rules match, the subscriber advances. If any rule fails, they exit the journey.
A typical 4-email welcome series over 10 days for new list subscribers. This is what a real journey looks like in practice.
Track every journey's performance with real-time statistics and enrollment details.
Time-release subscriber enrollment into journeys. Instead of enrolling everyone at once, spread enrollment evenly across a configurable time window using linear interpolation.
The system calculates how many subscribers should be enrolled by any given moment and batches them in groups of 100, spreading enrollment evenly across the window.
Create, pause, resume, and cancel drip schedules. View progress with total enrolled count and status. Timezone-aware scheduling (America/New_York).
A background worker runs every 60 seconds, automatically advancing pending drips to active, enrolling subscribers in batches, and completing drips when their window ends.
Build it once, let it run. Blanketcat handles the rest.
Request Access