Skip to content
Sendora Cloud
Create account
2026-05-30 · Docs

Automation page — wait-for-event / holdouts / in-app step claims retracted

  • Deep audit of the workflow engine vs marketing copy surfaced 4 over-claims: (1) "Send across every channel — Email / Push / SMS / In-App / webhook" — In-App is NOT a step type, only 4 senders + 4 utility steps. (2) "wait-for-event" — only fixed-delay `wait`. (3) "holdouts" — no holdout splits in code. (4) "Per-step A/B with statistical readout — winners auto-promote" — A/B lives in Push/Email template layer, not at the step level.
  • Real shape: 8 step types implemented in `apps/backend/src/modules/automation/step-executor.ts` — `wait`, `send_email`, `send_push`, `send_sms`, `update_profile`, `webhook`, `branch`, `ai_action`. 8 starter blueprints in dashboard template gallery. Trigger model is `{ eventType, filters }` with wildcard matching — every other module's events flow through this one type.
  • Customer.io + Braze + Iterable comparisons rewritten with honest capability tables. Each `whyStay` list now leads with the missing features as the primary reason to keep the competitor (wait-for-event, holdouts, drag-and-drop canvas).
  • Real wins kept: AI step type (`ai_action` with generate/decide/extract via Ollama Cloud + BYOK), 8-template gallery, pause/resume, promote.failed webhook, real-time event triggers reading the same bus every Sendora module emits to.