Automation conditions

A Condition step is a check: the workflow only continues past it when the rules match. If the rules do not match, that branch stops and BCL skips the steps after it. There is no “else” path, so to handle both cases, build two automations with opposite conditions.

Add a condition

You need an automation with a trigger already on the canvas.

1. Click Add Node and choose Condition under Flow Control. A Check Condition step joins the end of the workflow.

2. Double-click it to open Condition Settings.

3. Fill in a Condition Name (up to 20 characters). It becomes the step’s label.

4. Click Add Condition, then choose a Field, an Operator and a Value.

5. To add more rules, click Add Condition again and choose the Match Logic.

6. Click Save Condition.

   

Fields per trigger

The Field list depends on the trigger. Fields with a fixed list of values (statuses, forms, products) show a Value dropdown. The other fields take typed text or numbers.

Trigger	Fields you can check
Payment triggers (except Order Shipped)	Form Type, Form Name (ID), Product ID, Ticket ID, Booking Service ID, Payer Name, Payer Email, Payer Phone, Order Number, Payment Amount (Final), Subtotal Amount, Discount Amount, Additional Fee, Payment Gateway Fee, Shipping Cost, Total Items Count, Payment Status, Is Paid, Payment Channel, Coupon Code
Payment Successful, Payment Completed, Status Changed	All of the above plus Is Retry Payment
Order Shipped	Form Type, Form Name (ID), Product ID, Ticket ID, Booking Service ID, Courier, Tracking Number, Payer Name, Payer Email, Payer Phone, Order Number, Payment Amount (Final), Payment Status, Payment Channel
Event triggers	Event Form, Ticket ID, Attendee Name, Attendee Email, Attendee Phone, Ticket Name, Event Name, Event Type, Price Paid, Seat Number, Status, Order Number
New Lead Received	Form Title, Submission ID, and Custom Field for any lead form field
New Affiliate Registered	Affiliate Name, Affiliate Email, Affiliate Phone
Referral Approved, Referral Rejected	Affiliate Name, Affiliate Email, Order Number, Order Amount, Commission Amount, Referral Status
Payout Requested	Affiliate Name, Affiliate Email, Payout Amount, Payout Status, Total Referrals

For a lead form field, choose Custom Field. Type the field key in Field Key in the form name:id, for example email_address:2. The Variables list in the step shows the keys of your lead form fields.

Values you choose from a list

These fields offer fixed choices in Value:

Field	Choices
Payment Status	Pending, Failed, Successful, Cancelled, Completed
Form Type	Payment Form, Event Form, Booking Form, QR Terminal
Form Name (ID)	Your active forms, shown as [Payment] #67 - Form title (slug), and the same for events and bookings
Product ID, Ticket ID, Booking Service ID	Your active products, tickets or services, grouped by form
Is Paid, Is Retry Payment	Yes, No
Payment Channel	The payment methods BCL supports
Payout Status	Pending, Approved, Rejected, Completed
Event Form (event triggers)	Your active event forms

Product ID, Ticket ID and Booking Service ID match when that item is anywhere in the order, even with other items.

Operators

Number fields (amounts, counts, IDs, statuses) offer comparison operators. Text fields offer text operators.

Operator	Offered for	Passes when the field
Equals (=) / Equals	All fields	Is the same as the value
Not Equals (≠) / Not Equals	All fields	Is different from the value
Greater Than (>)	Number fields	Is bigger than the value
Greater Than or Equal (≥)	Number fields	Is the value or bigger
Less Than (<)	Number fields	Is smaller than the value
Less Than or Equal (≤)	Number fields	Is the value or smaller
Contains	Text fields	Includes the value anywhere
Does Not Contain	Text fields	Does not include the value
Starts With	Text fields	Begins with the value
Ends With	Text fields	Ends with the value
Is Empty	Text fields	Has no value (no Value box is shown)
Is Not Empty	Text fields	Has any value

Amount fields are plain numbers without “RM”, for example 500 or 49.90. Text comparisons are case-sensitive: KOPI10 does not equal kopi10.

Match logic

With two or more rules, Match Logic appears:

• All conditions must match (AND): every rule must pass.
• Any condition must match (OR): one rule that passes is enough.

A green note under the rules shows how BCL reads them, for example “Workflow continues if AND of the 2 conditions are met.”

How conditions run

A condition checks the data at the moment the workflow reaches it. After a Delay, BCL reads the transaction again, so a condition placed after a delay sees the latest status. This is how a reminder can check that an order is still unpaid before it sends.

Steps connected after a condition all run when it passes. BCL skips a condition with no rules, and its branch stops. The canvas marks the condition with “No conditions defined”.

Tips

A few habits keep conditions easy to read:

• Put the condition right after the trigger. When the condition filters the recipients, BCL schedules no delay for customers who will never receive the message.
• Use the trigger’s form filter before a condition. Specific Form on the trigger is simpler than a Form Name (ID) condition. With it, the automation does not run at all for other forms.
• Check a skipped run in the history. The execution details show the expected and actual value of every rule. So you can see immediately whether a value or an operator is wrong.

Common issues

Can I send a different message to customers who spend more than RM500?

Yes. Add a Condition with Payment Amount (Final), Greater Than (>) and 500, then the message step after it. Customers below RM500 stop at the condition. For the others, build a second automation with Less Than or Equal (≤).

How do I run an automation only when a customer buys a certain product?

Add a Condition with the field Product ID, the operator Equals (=), and choose the product in Value. It passes when that product is anywhere in the order.

My condition is never met. How do I see why?

Open the automation, click Overview, then View on an execution, and click View Response on the condition. A skipped condition shows each rule with the expected value, the actual value and whether it passed.

Related articles

• Automation triggers
• Automation variables
• Automation actions
• Check an automation's history