Skip to content
NewBranch

All work

NewBranch JourneyFlow

Client journeys triggered by real business events, with every step that could repeat a message held back until it is proven safe.

Category
Automation
Services
Agents and automation, Data foundations, Interfaces and adoption
Status
Builder live, messaging gated
Year
2026

Problem

Service businesses lose hours to the same follow-ups: welcome emails, reminders, invoices and chasing payment.

Automation that sends a reminder twice, or loses the event that should have triggered it, damages the relationship it was meant to help. Our first version passed events on a best-effort basis and treated any action with code behind it as ready to run.

Approach

  1. 01

    Record

    CRM events are written to an outbox in the same transaction as the change, delivered to each consumer with retries, and de-duplicated by the journey engine.

  2. 02

    Design

    Journeys are drawn on a canvas and saved through one versioned server command that checks named permissions and rejects stale edits.

  3. 03

    Validate

    Before a journey goes live the server checks its shape: one trigger, an exit, both branches on every condition, no orphan steps and no cycles.

  4. 04

    Gate

    An action runs live only after a reviewed change proves it is safe to retry. Task creation is cleared. Email, SMS and WhatsApp steps wait in draft.

What it does

conditions an action must meet before it may run live
6
action cleared so far: creating a task, all or nothing
1
journeys with cycles or half-built branches that can go live
0

Screens

Event log with the step each event triggered
One client's journey, step by step
Channels, approvals and limits