Skip to content
Automation

The builder knows nothing about WhatsApp — and that is the point

Every node in the palette is contributed by a plugin. Install one and your existing flows gain new capability; remove it and the engine tells you exactly what depends on it.

  • Message receivedtrigger
  • Ask AI to classifyai
  • Is it an order query?conditionYesNo
  • Send order statusaction
The palette

Nodes available today

This list is not fixed. It is whatever the plugins in your account contribute — which is why it grows without a product release.

Logic

4
  • ConditionBranch on any value from an earlier step
  • WaitPause for a fixed duration or until a time
  • For eachRepeat a branch over a list
  • TransformReshape data between steps

WhatsApp

3
  • Message receivedTrigger — inbound on any number
  • Send messageTemplate or session message
  • Assign to agentRoute the conversation to a person

CRM

4
  • Deal wonTrigger — a deal reaches won
  • Move deal stageAdvance or reset a pipeline stage
  • Add tagTag the contact in context
  • Create taskAssign a follow-up with a due date

AI

1
  • Ask AIClassify, extract, summarise or generate

Other channels

2
  • Send emailTransactional or marketing
  • Send SMSThrough your configured gateway

Developer

2
  • Call webhookPOST workflow data to your own service
  • Payment completedTrigger — a payment succeeds

Seventeen nodes ship with the default plugin set. Writing your own is a plugin, not a fork.

Recipes

Four flows most teams build in week one

Each of these is achievable with the visual builder alone — no code, no developer.

Order status without an agent

Trigger: Message received containing 'order' or 'where is'

  1. 1Ask AI to extract the order number
  2. 2Look up the order via a tool
  3. 3Send the status and tracking link
  4. 4If not found, assign to a human

Deflects the single highest-volume support question.

Abandoned cart recovery

Trigger: Cart abandoned for 60 minutes

  1. 1Check the contact has marketing consent
  2. 2Wait until inside quiet hours window
  3. 3Send the recovery template with the cart link
  4. 4If no reply in 24h, exit the flow

Recovers revenue without messaging people who said no.

Qualify and route an inbound lead

Trigger: Form submitted

  1. 1Create a contact and a deal
  2. 2Ask AI to score intent from the answers
  3. 3If score is high, assign to a senior rep
  4. 4Otherwise start a nurture drip

Reps spend their day on leads that are actually moving.

Post-payment onboarding

Trigger: Payment completed

  1. 1Move the deal to Won
  2. 2Send a receipt and next steps
  3. 3Create an onboarding task for the account owner
  4. 4Schedule a check-in for day 7

Nothing falls through the gap between sale and delivery.

The builder

Built to be debugged, not just demoed

Anyone can draw boxes and arrows. What matters is what happens when a flow misbehaves at 2am.

Palette from your plugins

Install a plugin and its nodes appear. Remove it and flows using them warn instead of silently failing.

Validation before save

Unreachable steps, missing config, cycles without a loop node and disabled plugins are all caught up front.

Run history

Every run keeps a step-by-step trace, so a failure tells you which node and why.

Variables everywhere

Reference any earlier step with {{node.field}} in messages, conditions and API calls.

Keyword triggers

Simple keyword bots for the cases that do not need a full flow.

Drip sequences

Multi-step nurture with delays, branching and exit conditions.

Getting started

From idea to running flow

Most first flows are live within an hour.

  1. 1

    Pick a trigger

    An inbound message, a CRM change, a payment, a schedule or a webhook from your own system.

  2. 2

    Add steps

    Drag nodes from the palette. Only nodes from plugins you have enabled appear.

  3. 3

    Validate

    The builder refuses to save a flow with unreachable steps or missing configuration.

  4. 4

    Watch it run

    Every execution keeps a trace, so debugging is reading a log rather than guessing.

Chatbots

Not everything needs a flow

For simple cases a keyword bot is faster to build and easier to reason about. Welcome messages, menu bots, fallback replies and out-of-hours responses live here — with analytics on every branch so you can see where people drop.

  • Welcome and fallback messages per number
  • Keyword and intent triggers with priority ordering
  • Menu bots with numbered or button options
  • Out-of-hours replies that respect your business hours
  • Per-branch analytics showing where conversations end
When to use AI instead

Keyword bot · Out of hours

Hi, are you open?

We are closed right now — we open at 9:30am. Reply 1 for order status, 2 to leave a message for the team.

Triggered
1,204
Chose 1
68%
Ended here
82%
Questions

Automation specifics

Tell us your most repetitive conversation

We will build that flow live on the call and show you the validation and run trace, including what happens when it fails.

No credit card required · 14-day trial · Cancel anytime