Run Your Business On Autopilot — Reminders, Reviews, And Rebooks That Send Themselves
A visual builder anyone on your team can use. Twelve triggers cover every booking, payment, and contact event. Seven actions handle SMS, email, WhatsApp, and tasks. Cooldowns and opt-outs on by default — your clients never get blasted.
Visual Builder. Real Catalog. Safety Defaults. Bulletproof Reliability.
The visual builder makes rules obvious. The trigger + action catalog covers real operational needs. Safety defaults prevent spam. The transactional outbox guarantees zero loss.
3-Pane Builder
WHEN palette on the left, IF conditions in the middle, THEN actions on the right. Drag, drop, reorder. Configurable delays on each action.
Triggers + Actions
12 trigger types covering bookings, payments, contacts, projects, and scheduled cron. 7 action types covering SMS, email, WhatsApp, tasks, tags, and notifications.
Safety Defaults
Per-rule cooldowns, daily and system caps, opt-out enforcement, and test-fire to the operator's phone before going live.
Reliability
Transactional outbox guarantees zero event loss even mid-deploy. Full audit log with manual re-fire from the log for incident recovery.
WHEN, IF, THEN — Visible At A Glance
Glue tools hide the logic in a long vertical scroll. Our 3-pane builder shows the whole rule on one screen — WHEN it fires, IF it should fire, THEN what happens. Drag to reorder, click to configure.
WHEN, IF, THEN Layout
Three vertical panes. Left: the trigger palette. Middle: the conditions that gate the rule. Right: the actions that fire. The whole rule fits on one screen.
- WHEN pane: pick from 12 trigger types
- IF pane: layer conditions with AND / OR logic
- THEN pane: chain up to 7 actions in order
- Visual flow makes review and audit easy
- Click any block to configure inline — no modal hell
- Save drafts, publish when ready
Drag-And-Drop Reorder
Reorder actions by drag-and-drop. Insert a delay between two actions, swap a step, or duplicate a block for an A/B variant — all without leaving the canvas.
- Drag to reorder any action in the THEN pane
- Insert delays between actions to pace the cadence
- Duplicate blocks for A/B variants
- Reorder conditions in the IF pane
- Branch logic: if A then X, else Y (in flight for early access)
- Undo / redo on every edit
Per-Action Delays
Configure a delay on each action — fire in 5 minutes, in 24 hours, on the next business day. The system handles the scheduling, retry, and recovery.
- Per-action delay in minutes, hours, or days
- Business-hours-only delays for staff-facing actions
- Scheduled to fire at a specific clock time
- Calendar-aware delays (e.g. "day before appointment")
- Survives platform restarts via persistent scheduling
- Visual timeline preview of the cadence
No credit card required
12 Trigger Types. 7 Action Types. Real Catalog, Not Marketing Copy.
Other platforms list "automations" as a feature but ship 3 hard-coded ones. We ship 12 trigger types — booking, payment, contact, project, and scheduled cron — and 7 action types. Configure any combination.
12 Trigger Types
Bookings, payments, contacts, projects, and scheduled cron. Each trigger surfaces its event payload as variables you can reference in conditions and actions.
- Booking: created, updated, cancelled, no-show
- Payment: succeeded, failed, refunded
- Contact: created, tag added, tag removed
- Project: status changed, milestone reached
- Scheduled: cron expression for time-based rules
- Variables from each trigger usable in conditions and templates
7 Action Types
Send SMS, send email, send WhatsApp, create task, mutate tags, fire in-app notification, fire webhook. Each action has its own configuration and templates.
- SMS — to contact, to staff, or to a number
- Email — to contact, to staff, with merge tags
- WhatsApp — same as SMS for messaging-first customers
- Task — create on a staff queue with deadline
- Tag mutation — add or remove tags on a contact
- In-app notification — surface in the staff console
Conditions + Variables
Conditions in the IF pane reference any variable from the trigger. Boolean logic with AND / OR. Date math, string match, numeric comparisons all supported.
- AND / OR / NOT logic across multiple conditions
- String, numeric, date, and boolean comparisons
- Date math: "booking time is in the next 48h"
- Tag-based conditions: "contact has tag VIP"
- Numeric thresholds on order total or LTV
- Saved variable references for reuse across rules
No credit card required
Safety Defaults That Stop You Spamming Your Customers
Automation without guardrails is a single rule away from disaster. Per-rule cooldowns, daily caps, opt-out enforcement, and operator-only test mode all ship enabled by default.
Per-Rule Cooldown
Configure a per-contact cooldown on every rule. Even if the trigger fires 10 times in an hour, the customer only gets the message once until the cooldown expires.
- Cooldown window per rule (e.g. 24h per contact)
- Cooldown enforced before the action fires, not after
- Configurable per-rule and per-action separately
- Skip-with-log behavior — no silent drops
- Customer-visible audit if anyone asks why no message fired
- Default cooldowns nudge you toward safety on new rules
Daily Caps + System Cap
A per-rule daily cap and a global system cap. Even if a rule misfires, the platform won't blast your customer base. Caps are visible on the rule and reviewable in the log.
- Per-rule daily cap (fires per day)
- Per-contact daily cap (messages they receive)
- Global system cap as a last line of defense
- Cap hit logs the skip with reason
- Per-cap alert notifications to the operator
- Override-with-reason flow for known one-off campaigns
Opt-Out Enforcement
Opt-outs are enforced at the action layer, not at the rule layer. A contact who opted out of SMS won't receive automation SMS no matter how many rules trigger.
- Opt-out checked before every send
- Per-channel opt-out (SMS, email, WhatsApp, voice)
- Per-category opt-out (marketing vs transactional)
- Transactional messages still flow as compliance allows
- TCPA-compliant opt-out keyword handling
- Audit trail of every opt-out event
Test-Fire To Operator
Before publishing, fire the rule against a sample event and route every action to the operator's phone — not to real customers. Verify the message, then publish.
- Pick a sample event from the last 7 days
- All actions redirect to the operator's phone
- Test-fire log distinguishes from production fires
- Iterate the rule with confidence before publishing
- Test-fire snapshot saved with the rule for audit
- Required by default on first publish
No credit card required
Reliability Engineering Behind The Pretty UI
Most automation tools lose events during deploys, network blips, or queue restarts. Ours uses a transactional outbox so the event is committed to the database in the same transaction that publishes it. Zero loss.
Transactional Outbox
Events are written to a Postgres outbox table in the same transaction as the originating change. A separate worker drains the outbox, guaranteeing at-least-once delivery.
- Outbox row written in the same DB transaction
- Worker drains outbox to the trigger evaluator
- Zero events lost on app crash, deploy, or restart
- Idempotency keys prevent duplicate-action effects
- Backpressure-safe — outbox absorbs traffic spikes
- Observable: lag metrics, drain rate, retry count
Full Audit Log
Every trigger, every condition evaluation, every action fired (or skipped, and why) lands in the audit log. Search, filter, and export for compliance or debugging.
- Per-fire log entry with rule, trigger, conditions, outcome
- Skip reasons logged (cooldown, cap, opt-out, condition fail)
- Searchable by rule, contact, date, outcome
- Per-contact view: what fired for them and when
- Exportable CSV for compliance and audits
- Configurable retention per your policy
Manual Re-Fire From Log
Something went wrong and the rule didn't fire? Open the audit log, find the missed event, click re-fire. The action runs as if the trigger had fired correctly the first time.
- Re-fire any logged event manually
- Re-fire respects current cooldowns and caps by default
- Override-with-reason for incident recovery
- Per-rule replay of historical events
- Bulk re-fire from a filtered log view
- Audit trail of every manual re-fire
No credit card required
Powered By Four Connected Modules
Automation is only useful when the rest of the platform fires the triggers and runs the actions. Each module connects to the engine.
Popular in these industries: