Every node in the builder belongs to one of three groups. Drill in for the per-node spec.

Builtin

Trigger, Wait, Conditional Split, Path, Exit (Cooldown / Handoff / Suppress).

Contact

Add Tag, Remove Tag, Add to Segment, Adjust Score, Assign Owner, Set Bot Autoreply.

Messaging

Send Email, Send (LinkedIn / Telegram).

​
Shared concepts

Every node has:
  • id — technical identifier (e.g. email-send)
  • name — display name in the palette
  • kind — action (do something then move on) or branch (split paths)
  • input schema — config fields shown in the drawer
  • output schema — values exported for downstream nodes via {{node.<id>.output.*}}

​
kind: action vs branch

  • action — runs, then exits via one outgoing edge.
  • branch — the Conditional Split node opens N paths; each path is then guarded by a Path node.

​
Node errors

When a node fails (e.g. email-send can’t deliver because a credential died, or add-to-segment can’t find the segment):
  • The run is marked failed.
  • A red activity bubble shows on the customer’s timeline.
  • The node’s “Errors” counter increments.
  • A retry policy applies per error type (transient: auto-retry, fatal: stop).