Campaign Nodes

If / Else

Route contacts down True or False paths based on workflow conditions.

The If / Else node evaluates conditions and routes the contact through either the True path or the False path.

When to use it

Use this node when the campaign needs deterministic branching.

Common examples:

  • branch by contact attribute or segment membership
  • route based on an event or message condition
  • check a response stored by Fetch API Data
  • separate eligible and ineligible contacts

Settings

  • Node name: optional display name shown on the workflow canvas.
  • Condition builder: rules that must match for the True path.
  • API output rules: optional rules based on upstream Fetch API Data output.
  • True path: output followed when rules match.
  • False path: output followed when rules do not match.

Simulation and execution behavior

Simulations evaluate the configured rules against the sample contact and available mock workflow output. Real executions evaluate the rules against live contact, event, message, segment, and workflow output context.

Best practices

  • Keep branch rules readable and name the node when the condition is business-specific.
  • Use Fetch API Data before this node when branching on external data.
  • Test both paths with simulations before publishing.

Time Window

Continue a campaign workflow only during allowed days and times.

Message Engagement Branch

Branch a workflow based on whether a campaign email was opened or clicked.