Workflow Nodes

What each node does and how to configure it in the UI

Previous

Workflow Nodes

Workflows are built visually. You’ll drag nodes onto the canvas, connect them, and configure simple options in the right‑hand panel. Below lists each node type, what it does, and the knobs you can control.

Triggers (campaign level)

  • Event Trigger
    • What it does: Starts the workflow when your app sends a specific event.
    • Configure: Event name; optional property filters (e.g., locale = en, placement = home); throttling or cooldown.
    • Tips: Start many campaigns from common events like app_opened, onboarding_completed, or feature_used.
  • Segment Trigger
    • What it does: Starts the workflow when a user enters a saved segment.
    • Configure: Segment to watch; optional re‑entry rules.
    • Tips: Great for lifecycle moments (trial starting/ending, inactivity, winbacks).

Actions

  • Show Flow (paywall)
    • What it does: Presents a paywall/flow from your Library.
    • Configure: Choose which flow to show; presentation options (e.g., allow dismiss); follow‑up path after dismiss/purchase.
    • Tips: Keep variants in your Library and swap without code changes.
  • Update Customer
    • What it does: Sets customer properties for targeting/analytics.
    • Configure: Key‑value fields (e.g., plan=trial, cohort=summer2025).
    • Tips: Use after a purchase or milestone to mark progress.
  • Send Event
    • What it does: Emits a synthetic event from the workflow.
    • Configure: Event name; optional properties.
    • Tips: Useful for analytics breadcrumbs or chaining other campaigns.
  • Call App Action
    • What it does: Calls into your app with a message (delegate). Use for custom integrations.
    • Configure: Action name; optional payload fields.
    • Tips: Coordinate entitlement refreshes or deep navigations post‑purchase.

Timing & Waiting

  • Wait (Delay)
    • What it does: Pauses before moving to the next node.
    • Configure: Duration (seconds/minutes/hours).
    • Tips: Add breathing room between shows; avoid stacking prompts.
  • Time Window
    • What it does: Only continues during specific dates/times.
    • Configure: Start/end date and time; timezone (device or UTC); days of week (e.g., Mon–Fri only).
    • Tips: Schedule promotions; avoid showing flows overnight or during quiet hours.
  • Wait Until
    • What it does: Waits for one of several conditions to become true and then follows that path; optional timeouts per path.
    • Configure: One or more conditions (e.g., “completed onboarding”, “made a purchase”); optional max wait per condition; path order.
    • Tips: Place this after a Show Flow to react differently if a user buys, dismisses, or triggers a milestone.

Branching & Logic

  • If / Else (Branch)
    • What it does: Routes users based on a single condition.
    • Configure: Condition (e.g., “is in segment: power_users”, “event count of feature_used ≥ 3”).
    • Tips: Keep conditions simple; combine with Wait Until for richer funnels.
  • Multi‑branch
    • What it does: Tries multiple conditions in order and routes to the first match; includes a default path.
    • Configure: An ordered list of conditions; default path.
    • Tips: Model funnel stages (prospect → trial → subscriber → default).
  • Random Split (A/B/n)
    • What it does: Splits users into cohorts by percentage.
    • Configure: Number of variants and their split (must total 100%).
    • Tips: Use for creative tests or pricing experiments; pair with Show Flow.

Control

  • End (Exit)
    • What it does: Stops the workflow.
    • Configure: Optional reason label (for analytics/readability).
    • Tips: End each path explicitly to keep graphs clear.

Good to know

  • Conditions are built with a visual editor (segments, events, user properties). You don’t need to write expressions.
  • Campaigns can have multiple active workflows; priority/conflict rules decide which one wins if several want to show a flow.
  • Respect frequency: add Wait or Frequency policies to avoid over‑showing.

See also