Automation

WhatsApp Automation and Drip Flows

Build visual sequences that nurture leads, follow up on cart abandonment, and answer common questions automatically - on WhatsApp, 24 hours a day. No code, no developer, no waiting.

Start Free Trial - 14 days free See a Demo

Flow Builder

⚡

Lead Form Submitted

💬

Send Welcome Message

🤔

Replied within 24h?

No Reply

⌛

Day 3 Follow-up

Replied

🌟

Tag: Hot Lead

Build, branch, drip

Drag, drop, publish

A flow builder simple enough for marketing, deep enough for revenue ops. The same canvas runs your first welcome series and your hundredth re-engagement program.

Triggers

Start on the moment that matters

Choose what kicks off a flow: a fresh contact, an inbound keyword, a tag being added, a date in the future, or an external API call from your CRM. Mix multiple triggers per flow if you want one journey to serve many entry points.

✓
New contact, keyword reply, tag, schedule, or API
✓
Mix multiple triggers in one flow
✓
Per-contact daily caps to protect WABA quality

Trigger Config

⚡

Keyword reply

Inbound contains "PRICING"

✓

👤

New contact created

Source: form, API, or import

🏵

Tag added

"cart-abandoned"

📅

Schedule

Weekly, Mon 09:00 IST

Branching

One flow, every possible response

The Wait for Reply node pauses the flow until the contact responds. Branch on keyword, button tap, or template button index. Each path is independent: different messages, different waits, different conversions tags.

✓
Branch on keyword, button, or condition
✓
Nested conditions for fine-grained routing
✓
Auto-tag contacts based on which path they took

Branch Logic

🤔

Did they tap a button?

"Check eligibility"

📝

Send criteria + qualify

"Talk to counselor"

📱

Book call link

tag: qualified

tag: hot-lead

tag: cold

Drip sequences

Nurture for days, not minutes

A WhatsApp drip is just a flow with waits between steps. Day 0 welcome, day 2 case study, day 5 social proof, day 14 re-engagement. Each step respects opt-outs, per-contact caps, and your WABA messaging window.

✓
Configurable wait per step (minutes to weeks)
✓
Skip steps when contact already converted
✓
Quiet-hours respect to avoid 2am pings

14-day Welcome Drip

D0Welcome + introSent

D2Case study #1Sent

D5Pricing breakdownSent

D7Schedule a callLive

D10Social proofQueued

D14Final offerQueued

How it works

Three steps from blank canvas to live flow

The flow builder is the same one our power users run 50-node enterprise workflows in. It scales down to a three-step welcome just as gracefully.

Pick a trigger

Choose what kicks off the flow. Lead form submission, keyword reply, schedule, API call, or a tag being added to a contact.

→

Drop your nodes

Drag messages, waits, conditions, and tag actions onto the canvas. Connect them with arrows. Branch on keyword or button tap. Save as draft.

→

Publish + monitor

Hit Publish. New triggers immediately enroll matching contacts. Watch enrollments, completion, and per-node drop-off on the analytics panel.

FAQ

Flow builder questions

Do I need a developer to build flows?

No. dripBot ships a visual drag-and-drop flow builder. Drop nodes for triggers, messages, waits, conditions, and tags onto a canvas, connect them, and publish. Most teams build their first useful flow in under 15 minutes.

What can trigger a flow?

Triggers include a new contact being created, a contact replying with a keyword, a tag being applied, a date or recurring schedule, or an external system calling the dripBot API. You can mix triggers in the same flow.

Can flows branch on what a contact replies?

Yes. Use the Wait for Reply node to pause for an inbound message, then branch on keyword match, button tap, or which template button the contact pressed. Each branch is its own path with its own messages and waits.

Are drip sequences limited in length?

No fixed cap. A drip flow can be a 3-day welcome series or a 60-day re-engagement program. Each step waits the configured duration, then runs whether or not the previous step got a reply.

Can I A/B test two flow variants?

You can run two flows in parallel and assign contacts via tags or a percentage split using the API. Native A/B branching is on the Phase 2 roadmap.