Automations

Set the flow once. Let it work while you don’t.

A visual canvas for multi-step journeys across every channel — with real sends, delays, conditions, and webhooks, all running on a durable queue.

Wait: minutes → weeks Conditions: 8 operators Webhook (GET / POST / PUT)
Flow canvas — a live journey
QuickGrow's automation builder canvas showing the 'Abandoned Cart Recovery' journey: a trigger, a one-hour wait, a 'Send Email' step, a six-hour wait, a WhatsApp message, a one-day wait, an SMS, and a final 'Add Tag' step — each card naming the template it sends.

No placeholder steps. Every node does something.

Send email, SMS, or WhatsApp — each dispatched as a real, tracked message. Wait minutes to weeks, branch on an if/else condition, add or remove tags, update contact fields, add or remove a contact from a segment, or call an external webhook (GET / POST / PUT). Eleven actions in all — every node does real work.

Send email

Dispatched on the durable queue as a real, tracked message — opens, clicks, and delivery recorded.

Send SMS

A real SMS through your connected provider, with the same delivery tracking as a campaign send.

Send WhatsApp

Text, media, or template messages over the official Meta Cloud API — metered against your prepaid wallet.

Wait

Pause a contact in the flow for minutes, hours, days, or weeks before the next step runs.

Condition (if / else)

Branch on eight operators — equals, contains, greater/less than, is-empty, and more — so each contact takes the path that matches.

Tag & contact updates

Add or remove tags and update contact fields as a contact moves through the journey.

Segment membership

Add a contact to a segment or remove them from one, mid-journey, as their state changes.

Webhook (GET / POST / PUT)

Call an external URL mid-flow with a GET, POST, or PUT request to notify or sync another system.

Kick off on a signal — or when you decide.

Enroll a contact when they’re created or updated, when a tag is added or removed, when they enter or leave a segment, when they open or click an email, or when a form is submitted. Date-based triggers — renewals, anniversaries, and other milestones — run on a scheduler, and you can always enroll a contact manually or through the API.

Date-based scheduler Tag & segment eventsManual / API
Ways a contact enters a flow
On a date

Renewal, anniversary, or milestone — released by the scheduler.

On a tag or segment

A tag added or removed, or a contact entering or leaving a segment.

On email engagement

A contact opening or clicking an email, or submitting a form.

Manually or via the API

Enroll a contact by hand or from your own app or backend with an API call.

Built on a durable queue — so a hiccup isn’t a lost message.

Every step runs on a durable BullMQ queue with three automatic retries and backoff, plus per-step run logs, so you can see exactly what each contact did and when. Every send is a real, tracked message — not a simulation.

3 retries with backoff

Steps run on a durable BullMQ queue; a failed step retries up to three times with backoff instead of silently dropping.

Per-step run logs

Every step a contact reaches is logged, so a journey is auditable end to end.

Real tracked sends

Each email, SMS, or WhatsApp step dispatches a real message with the same delivery tracking as a campaign.

Draw the journey once. It runs itself.

Product screens shown across this site are captured from the live application using a demo workspace. All names, contacts and figures in them are synthetic.