Automations
Banchurn runs on an event bus, and Automations is how you program it. Build journeys on a canvas: trigger on any product event, or the moment a customer enters or leaves a lifecycle state: free-and-active, at-risk, power-user. Then wait on timers, branch on conditions, and fan out to actions: send an email or an in-app message, update a trait, move a customer between segments, or fire a webhook. Actions emit events, so journeys compose into larger ones.
Lifecycle marketing is a hundred tiny manual follow-ups
Send the welcome. Nudge the customer who stalled onboarding. Win back the one whose usage dropped. Escalate the account that just went at-risk. Each is trivial; together they're a full-time job that never scales past your first few hundred customers.
The flow, end to end
Trigger
An event hits the bus: a signup, a downgrade, or a customer entering the at-risk state.
Evaluate
The engine checks each automation's trigger and enrollment filter for a match.
Branch
Condition nodes route the customer; timer nodes hold them until the wait elapses.
Act
Action nodes execute, and emit new events, so journeys chain without glue code.
What's in the box
Event & lifecycle-state triggers
Start a journey on any product event, or the moment a customer enters or leaves a segment: a signup, a downgrade, entering at-risk.
Visual builder
Compose triggers, conditions, delays, and actions on a canvas. No code.
Conditional branching
Route each customer down the right path with all / any / not condition trees.
Timers & waits
Hold a customer for hours or days; a background processor advances them on schedule.
Rich, multi-channel actions
Send an email or an in-app message, update traits, change segment membership, or fire a signed webhook.
Enrollment filters
Scope exactly who enters a journey so the right customers get the right sequence.
One event bus, drained by a processor, powering everything
Every meaningful change emits an event. A background processor drains the stream, advances waiting customers as their timers expire, and fans work out. Campaigns, churn scoring, and automations are all consumers of the same rail, which is why an action in one journey can trigger another.
- ✓Durable event stream with a polling step processor
- ✓Waits advanced on schedule: no lost enrollments
- ✓Actions emit events, so automations compose
A canvas anyone on your team can reason about
Triggers, conditions, delays, and actions are nodes you wire together: no code, no YAML. Condition nodes carry all/any/not trees, timer nodes hold a customer for hours or days, and an enrollment filter decides precisely which customers ever enter the journey in the first place.
- ✓Trigger on any event or lifecycle-state change; a filter scopes entry
- ✓All / any / not condition trees route each path
- ✓Delays and scheduled sweeps advance customers over time
Campaigns
Batch or triggered, to a segment or a list: one campaign model covers every send you need.
Learn moreAccount signals
Score every account on fit, usage, intent, and risk, so you see who's ready to expand and who's slipping toward churn.
Learn moreSegments & lists
Dynamic, rule-based segments that keep themselves up to date, plus static lists you control by hand.
Learn moreStop losing customers you could have kept
Book a walkthrough and see churn prediction, account signals, segments, campaigns, destinations, and Autopilot working together, on one platform.