Use the Flow Editor to combine delays, email and LINE messages, and conditional branches in a scenario. You do not need to upgrade to the Plus plan to use the Flow Editor.
This guide covers opening and using the Flow Editor, including an example that sends the second and third welcome emails only to customers who have not placed an order.
Before you edit
After you save a scenario in the Flow Editor, you cannot return to editing it in the standard settings form. Duplicate an active scenario and review the changes in a draft before switching over.
Create the email and LINE messages you want to send in advance. Before activating a duplicate, check the status and trigger of both scenarios to avoid duplicate messages.
Open the Flow Editor
- Open the scenario you want to edit from Scenario in StoreCRM.
- Under Settings, find Details and select (Advanced) Edit with Flow Editor. For a scenario already in flow mode, select Edit Flow.
- Review the mode-switch confirmation before continuing. For a new scenario, save a draft first, then open its detail page.

Read the canvas and add nodes
A node is a block that performs a task such as waiting, sending a message, or evaluating a condition. Execution follows the connections from the trigger. The scenario type determines the trigger, which cannot be changed or deleted in the Flow Editor.
Select a node to show its settings on the left. Click an empty area of the canvas to return to scenario-wide settings such as the scenario name and execution conditions.

- Click + where you want to add a node.
- Choose a task in Add Node.
- Select the new node and enter its name and required settings.

| Main node | Usage |
|---|---|
| Send message | Select an email template and/or a LINE message. To send email only, leave the LINE message unselected. |
| Send email | Send the selected email. |
| Wait | Wait for an interval after the preceding task before continuing. |
| Wait until | Wait until the configured date or time condition is met. |
| Conditional | Follow YES when the condition matches and NO when it does not. |
| Filter | Continue only when the condition matches. Otherwise, end the remaining tasks. |
| Generate coupon | Generate a coupon for subsequent email or LINE messages. |
| Check coupon | Check whether the coupon generated in this scenario has been used, and stop subsequent tasks if it has. |
Coupon usage and purchase status are different conditions. To stop messages after any purchase, including one without a coupon, use a customer condition such as Order Count.
Execution conditions, Conditional, and Filter
| Setting | When it is evaluated | If it does not match |
|---|---|---|
| Scenario-wide execution conditions | When scenario execution starts | The scenario does not run for that customer, including the first message. |
| A Conditional node in the flow | When execution reaches the node | Execution follows NO. |
| A Filter node in the flow | When execution reaches the node | The remaining tasks end for that customer. |
Scenario-wide execution conditions are not re-evaluated before every email. To send the first message and stop later messages depending on purchase status, place a Filter after the wait and before the message node.
Conditional and Filter nodes offer customer, order, and other fields depending on the scenario type. Combine conditions with AND, OR, and NOT. For a registration-triggered scenario, use Customer > Order Count rather than an Order field.
View available scenario conditions
Example: send follow-ups only to customers with no orders
In this example, the first email is sent after registration, the second three days later, and the third after another three days. Set the delay before the first email to suit your schedule.
- Place the first email node after the registration trigger.
- Add Wait after the first email and set Wait interval to 3 days.
- Add a Filter after the wait and set Customer > Order Count > equal to > 0.
- Place the second email node after this Filter.
- Add another Wait node for 3 days.
- Add the same Order Count = 0 Filter before the third email, then place the third email node after it.


Customers who order after email 1 stop before email 2. Customers who order after email 2 stop before email 3. A single check before email 2 does not check for later orders, so add a Filter before each follow-up.
Order Count = 0 means the customer has never placed an order, including before registration. Evaluation uses information already synchronized to StoreCRM, so a recent Shopify order may take time to appear.
More about delays and percentage branches
For Wait, choose seconds, minutes, hours, or days and enter an integer. Seconds support values from 0 to 8,640,000; 0 seconds continues immediately.
In a Conditional node, choose Logic (A/B test etc.) > Go to YES with a percentage to set the share that follows YES to an integer from 1% to 99%. Presets of 95%, 90%, 80%, and 50% are available. Values of 0, 100, and decimals are not supported.
Connect a message node to YES and leave NO without a message to compare delivery and non-delivery groups. Assignment is stable for the same customer and condition, but small groups may not match the exact percentage. Compare assigned customers separately from actual sends, which also depend on consent and other checks.
Test, save, and activate
- Select Test this scenario at the top of the editor.
- Under Enter test conditions, check both Order count = 0 and an order count of 1 or more. Reuse a past event is also available for supported triggers.
- On Review execution, check any real-send or coupon-issuance selections and recipients before running the test. Leave real sending and issuance unselected when checking the path only.
- Review the execution path and condition results. Tests skip waits, so separately verify purchases made during a real waiting period using updated customer data.
- Select Save when the flow is ready. Saving and activation are separate actions. Check the settings and potential duplicate sends on the detail page, then set the status to Active.

Errors block saving. If a warning appears, review the affected nodes and paths before saving. Names such as Wait 3 days and Continue if order count is 0 make the flow easier to review.