Cookiebees
4Act: Turn it into the next sale

Workflows

When this happens, do that.
And know it will work.

Pick a trigger, add conditions, choose what happens: a WhatsApp, an email, an alert to the owner, a signal to the ad platforms. Before you save, you see how many real events it would have caught. Once it is live, a broken step is named in plain words before a customer misses a message.

30-day free trialNo card requiredSet up in minutes

Will this workflow actually fire, and for whom?

Why did my WhatsApp follow-up stop going out?

Order delivered → ask for a review · runson
When: order deliveredIf: prepaidWait 2 daysWhatsApp the customer
14:07order #10482 · WhatsApp sent
13:52order #10481 · Not sent: this number replied STOP to your WhatsApp messages.
12:30order #10478 · WhatsApp sent
11:05order #10475 · Skipped: exit condition met while waiting.
10:41order #10473 · WhatsApp sent
Every run says what it did, and every skip says why, on the record it happened to.

Can I stop messaging someone the moment they buy?

Which workflows failed this week, and why?

What it is worth

Automations you do not have to babysit.

No silent failures

Workflows that failed this week sit at the top of the list with the reason in plain words, and a morning email can bring them to you.

No dead rules

A workspace is only offered the triggers it can fire. A workspace without a store is never offered order triggers.

No messages after the sale

Exit rules are checked against the record as it is now: someone who bought during the wait gets no reminder, and a sequence stops when they reply.

Test fire

Every step, on a real record. Nothing sent.

A test fire takes the latest real event the workflow received and runs it through: the conditions judged for real, and each step checked the way the live send would check it. A template Meta has paused, a lead with no phone, a blank variable in the message: each is named against that record. This was a test, so nothing was sent.

  • Conditions checked against 30 days of real events, before you save
  • Each step checked the way the live send checks it
  • Template variables filled from this record, not the sample
  • Nothing sent, written or scheduled
Test fire · Order delivered → ask for a reviewdry run

On order #10482 from 3 Oct, the latest real event this workflow received.

Conditions

Payment method is prepaid

met

Wait 2 days

would wait, then go on

ok

WhatsApp the customer

The WhatsApp template "review_ask" is paused by Meta.

would fail

This was a test, so nothing was sent.

Each step is checked the way the live send would check it: the template, the number, every variable filled from this record.

Needs attention

A broken workflow, found before a customer notices.

Every night, each switched-on workflow is judged on recent real records, after 02:00 in your own time zone. Anything that would fail or can never fire goes on the Needs attention card, with the reason in plain words and a link to the workflow. Turn on the morning note and your admins get it by email too.

  • This week’s failed runs, each with its reason
  • Would fail, can never fire, may never fire
  • Check now, whenever you like
  • A morning email to admins, off unless you turn it on
Workflows · needs attention
Not checked yet tonight.

Order delivered → ask for a review

on
last ran yesterday

Checkout abandoned → email in 1 hour

on

nothing found

Email the admins each morning

The check judges every switched-on workflow on recent real records, after 02:00 in your own time zone. It sends nothing.

Exit rules

They bought. The reminder never goes.

A wait is not a timer that fires blindly. Before the next step, the exit rules are checked against the record as it stands now, so a shopper who ordered during the wait is dropped, and the run says why. Sequences stop the same way when a lead replies, reaches a stop stage or opts out.

  • Exit when they buy, reply or opt out
  • A number that replied STOP on WhatsApp is skipped
  • Every skipped step recorded, with its reason
  • Switch a workflow off and its waiting runs are cancelled
Run · Checkout abandoned → email in 1 hourwaiting

Checkout started, not paid

10:14

cart ₹2,499 · a known customer

Wait 1 hour

10:14

the run waits

Order #10482 placed

10:52

the same customer, on their own

Email the customer

11:14

exit condition met while waiting - remaining steps skipped

The exit rule is checked against the record as it is at the next step, not as it was when the trigger fired.

Workflows, on your own site.

Start a workspace and watch it work on your next order or lead, or let us walk you through it.

Switching it on

From a template to switched on.

  1. 1

    Start from a template

    Recovery follow-ups, purchase signals, lead welcomes, meeting reminders, AI calls: each a full workflow you can edit.

  2. 2

    Write the conditions

    Under them: how many of the last 30 days’ real events they would have let through, and the rule that stopped them if none.

  3. 3

    Switch it on

    A WhatsApp template Meta has not approved blocks this. Save it switched off and switch it on once Meta approves.

  4. 4

    Leave it to the nightly check

    If a step would fail or the trigger can never fire, the Needs attention card says so the next morning.

Inside the module

Inside Workflows

Every trigger, action and check below is on the Workflows page today.

Triggers

Orders, deliveries, refunds, checkouts, leads, meetings, calls and messages, offered only when the workspace can fire them

Actions

WhatsApp, email, owner alerts, tasks, webhooks, AI calls and signals to the ad platforms

Template library

Ready workflows for stores and for lead generation, grouped in folders

Condition check

How many real events in 30 days the conditions would let through

Test fire

A dry run of every step on the latest real record

Needs attention

Failures in plain words, a nightly check and a morning email

The test fire and the nightly check judge every step with the same checks, on real records, and neither one ever sends a message.

Where this sits

One of the four steps an order goes through.

Every feature reads the same identity. Open any of them; each has its own page.

Put the next sale on autopilot, and keep an eye on it

When this happens, do that.Tested before it matters.

Start from a template, test it on a real record, and switch it on. If a step ever breaks, the workflow list says so in plain words.