Automation recipes

Each recipe below is a complete automation you can copy: the trigger, any condition or delay, the action, and the message text with variables. Every recipe was built and run on the BCL demo account.

If you have never built an automation, read Create an automation first. For the full list of options, see triggers, conditions, actions and variables.

All recipes

Pick a recipe by what should happen and when:

Recipe	Trigger	Then	Start from
Send a thank-you email after payment	Payment Successful	Email the customer	Thank You Email on Payment template
Alert your team about new orders	Payment Successful	Email your team (or WhatsApp)	Blank
Remind customers about unpaid orders	Payment Cancelled	Email the customer a link to pay	Blank
Follow up on failed payments	Status Changed	Condition: status is Failed, then email	Incomplete Payment Follow-up template
Remind participants before your event	Participant Created	Delay until the day before, then email	Blank
Send class tips after a booking	Payment Successful (booking form)	Condition: the booked service, then email	Blank
Follow up on new leads	New Lead Received	Email, wait 3 days, email again	Blank
Deliver a digital product by email	Payment Successful (one form)	Email the download or protected link	Blank
Send the tracking number when an order ships	Order Shipped	Email the courier and tracking number	Blank
Welcome new affiliates	New Affiliate Registered	Email the affiliate	Welcome New Affiliate template
Send paid orders to your CRM	Payment Successful	HTTP Request to your CRM	Blank

Other ready-made setups are on the Templates panel, such as Wabot Payment Notification, Google Sheets Transaction Log and Lead Form SMS Notification. See Automation templates.

Note

Booking reminders before the session are not an automation: an automation can only wait a fixed time after its trigger or until one fixed date. BCL already sends booking reminder emails 1 day and 1 hour before each booking. Check them in your booking form’s Notifications page, on the Email Templates tab.

Before you switch a recipe on

A new automation is active as soon as you create it, and one made from a template starts inactive. Either way:

1. Use the test box in each message step (Test Email, Test Wabot and so on) to send yourself a sample.
2. Make a test purchase or submission while your team is in Test Mode.
3. Open the automation, click Overview, and check the run in Execution History. See Check automation history.

A team can have up to 20 automations. Rather than one automation per form, use one automation with the trigger’s form filter, or a Form Name (ID) condition.

Tips

A few habits keep your automations tidy:

• Start with one message step and add more later. A short, working automation beats a long one that fails at step four.
• Name automations after what they do. Call one “Unpaid Order Reminder”, for example, and the Automations list reads like a to-do list.
• Switch off rather than delete. If you might need an automation again, switch it off. Deactivate keeps the workflow and its history.

Common issues

Do I need to build every automation from scratch?

No. Several recipes start from a built-in template: click Templates on the Automations page and pick the one the recipe names. Each recipe says whether a template covers it.

Will an automation run for all my forms?

Yes, unless you narrow it down. Double-click the trigger and pick a Payment Source Type and Specific Form, or an event or lead form, to limit it.

Related articles

• Create an automation
• Start an automation from a template
• Automation triggers
• Automation actions