Iterable Workflows: Scalable Automation for High-Growth Brands

Iterable’s Workflow Studio is the operational heart of the platform. Every automated programme — onboarding sequences, lifecycle campaigns, cart abandonment, re-engagement — is built and managed here. For high-growth brands that need automation that scales with their user base without constant manual intervention, Iterable’s workflow architecture is well-designed and genuinely powerful.

This guide is a practical walkthrough of Iterable’s Workflow Studio: what each node type does, how to build effective event-triggered automations, and the specific patterns that work best for e-commerce and SaaS brands.

Iterable’s Workflow Studio: Core Concepts

Workflow Studio is accessed from the main Iterable navigation under Messaging → Workflows. Every workflow you build contains a combination of the following node types:

Entry Events (Triggers)

The entry event defines what causes a user to enter the workflow. Iterable supports three primary trigger types:

Custom Event Entry: A custom event (sent to Iterable via API) triggers workflow entry. This is the most flexible and powerful entry type. Any action a user takes — in your app, on your website, or in your backend system — can be sent to Iterable as a custom event and used to trigger a workflow. Examples: purchase_completed, free_trial_started, cart_abandoned, subscription_cancelled.

List Entry: Users enter the workflow when they are added to a specific Iterable list. Useful for batch workflows where you define an audience (a re-engagement segment, a win-back cohort) and want to run a defined sequence for that group.

API Trigger: An explicit API call directly targets a specific user for workflow entry. Used when you need precise, individual-level triggering — for example, triggering a password reset workflow from your authentication system.

Filter Nodes

Filter nodes check whether a user meets a defined condition at that point in the workflow. If the condition is met, the user continues down the “yes” path; if not, they go down the “no” path.

Filters can check:

Custom user profile attributes (e.g., plan_type == "premium")
Custom event data from the entry or a subsequent event (e.g., whether a specific event has been fired for this user since workflow entry)
Subscription status for a specific channel or message type
Whether the user is in a specific list

Filters are where workflow intelligence lives. Without filters, a workflow sends the same sequence to every entrant regardless of their behaviour or status. With well-designed filters, the workflow adapts — sending different messages to users in different states, skipping steps for users who have already completed an action, or routing users to entirely different paths based on their profile.

Delay Nodes

Delay nodes pause workflow progression for a defined period: minutes, hours, or days. Every workflow needs thoughtfully placed delays — immediate follow-up to every message creates an overwhelming experience, and delays allow time for the user to respond before sending the next touchpoint.

Iterable also supports delay-until logic: pause until a specific time of day (useful for ensuring messages arrive during business hours) or pause until an event occurs (wait until checkout_completed fires before proceeding — if it never fires, proceed after a defined maximum wait).

Message Nodes

Message nodes are where emails, SMS messages, push notifications, and in-app messages are configured and sent. Each message node specifies:

The channel (email, SMS, push, in-app)
The specific template or message to send
Any personalisation tokens to include

Experiment Nodes

Experiment nodes split workflow traffic between two or more paths for A/B or multivariate testing. You define the traffic split percentage, and Iterable tracks performance per path in the workflow analytics dashboard.

Experiment nodes are essential for data-driven workflow optimisation. Rather than guessing whether a 1-day or 3-day delay between emails performs better, you can test both simultaneously with a controlled split.

Update User and Update Cart Nodes

Beyond messaging, workflows can take data actions: updating user profile attributes or cart data. The Update User node allows workflows to write back to the user profile — for example, changing a user’s lifecycle_stage attribute when they complete a key milestone, or incrementing a counter attribute.

Event-Triggered Workflow Entry

The most powerful entry events in Iterable are custom events, because they tie workflow entry directly to user behaviour rather than a time-based schedule or manual list upload.

Setting up event-triggered entry requires:

Defining the event name and schema (what data fields accompany the event)
Instrumenting your app, website, or backend to fire the event via Iterable’s API when the behaviour occurs
Configuring the workflow to trigger on that event

The event data payload is accessible inside the workflow as personalisation data. A purchase_completed event might carry product_name, order_value, order_id, and product_category — all of which can be used in personalised email templates or as conditions in filter nodes.

Building a User Onboarding Workflow for SaaS

Onboarding workflows are the highest-ROI automation for most SaaS brands. The period immediately after signup is when users are most motivated to learn the product — and when churn risk is highest if they don’t experience value quickly.

Entry event: user_signed_up

Structure:

Email (immediate): Welcome email. Brand introduction, key value proposition, single clear action to take next (e.g., “Complete your profile”).
Delay 1 hour.
Filter: Has profile_completed event fired? If yes, skip to Step 6. If no, continue.
Push notification (if app user): Prompt to complete profile with deep link.
Delay 24 hours.
Filter: Has first_key_action event fired (the primary activation event for your product)? If yes, route to active user track. If no, continue.
Email: Feature education — the single most important thing users need to understand to experience value. Focus on one feature or outcome, not a product tour.
Delay 48 hours.
Filter: Activation event fired? If yes, active user track. If no, continue.
Email: Social proof + use case email. “Here’s how [similar companies] are using [product] to achieve [outcome].”
Delay 72 hours.
Filter: Still no activation? Route to high-touch branch (sales team task creation) or self-serve help email.
Update User node: Set onboarding_status = completed or at_risk based on final filter outcome.

The Update User node at the end is valuable — it writes the onboarding outcome back to the user profile, making it available for future segmentation and triggering further workflows.

E-Commerce Automation Patterns in Iterable

Cart Abandonment

Entry event: cart_abandoned (custom event fired by your e-commerce platform when a session ends with items in cart and no purchase).

Three-email sequence over 5 days:

Email 1 (1 hour after abandonment): Cart reminder with personalised product images and a single “Complete your purchase” CTA.
Email 2 (24 hours): Social proof — ratings, reviews, or “in demand” signals for the abandoned product.
Email 3 (72 hours): Escalated incentive (free shipping, small discount, or another offer appropriate to your margin).

Filter at each step: Has purchase_completed fired since entry? If yes, exit the workflow immediately.

Browse Abandonment

Entry event: product_viewed (fired when a user views a product detail page without adding to cart, with a minimum time-on-page threshold to filter out accidental visits).

Two-email sequence over 48 hours:

Email 1 (4 hours): Product reminder with personalised details (product name, image, price) from the event data. Include 2–3 related products.
Email 2 (24 hours): “Still thinking about it?” with stronger social proof and urgency signal (if applicable).

Post-Purchase

Entry event: purchase_completed

Five-email sequence over 21 days:

Email 1 (immediate): Order confirmation (or link to transactional system if order confirmation is handled separately).
Email 2 (Day 3): Product onboarding or care instructions.
Email 3 (Day 7): Review request with personalised product reference.
Email 4 (Day 14): Cross-sell recommendations based on purchase category (pulled from user profile or event data).
Email 5 (Day 21): Loyalty programme invitation or repeat purchase nudge.

Monitoring Workflow Performance with Iterable Analytics

Iterable’s workflow analytics are accessible from the workflow detail view. Metrics available per workflow:

Total entries, active users, completed exits, and goal conversions
Conversion rate (entries to goal completions)
Per-node send count, delivery rate, open rate, click rate, and unsubscribe rate
A/B experiment performance comparison (for workflows using experiment nodes)

For e-commerce brands, the key metric is revenue per workflow entry — how much revenue can be attributed to users who entered the workflow, compared to a control group who didn’t. This requires integrating Iterable with your revenue data, typically via custom conversion event tracking.

For SaaS brands, the key metric is activation rate — what percentage of workflow entrants achieve the defined activation event before the workflow ends?

Iterable’s workflow system rewards teams who invest in thoughtful architecture. The combination of event-triggered entry, filter-based branching, experiment nodes for continuous testing, and multi-channel message delivery creates an automation capability that genuinely scales with a high-growth business.

At Excelohunt, we build and optimise Iterable workflows for e-commerce and SaaS brands — from initial automation architecture to ongoing A/B testing and performance improvement. If you want to build workflows that drive measurable revenue and activation, we can help.

Looking to implement these strategies with expert support?

Iterable — learn how we implement this for clients
Email Automations — learn how we implement this for clients Get a free audit →