Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.yuko.so/llms.txt

Use this file to discover all available pages before exploring further.

Where to find this: Inside any workflow, the first node (trigger) and any binary nodes you add (conditions).

Triggers

A workflow has exactly one trigger node, set when the workflow is created. The trigger defines the event that starts the flow.

Available triggers

TriggerFires when
Order placedA customer completes an order
Customer createdA new customer record is created
Points earnedYuko credits points to a customer
Points redeemedA customer redeems a reward
VIP tier changedA customer moves between tiers
Membership unlockedA customer’s membership becomes active
Membership lostA customer’s membership ends
Customer inactive for X daysCustomer’s last activity exceeds the threshold
BirthdayThe current date matches the customer’s birthday
AnniversaryThe current date matches the customer’s signup anniversary

Choosing a trigger

  • Use Order placed when the workflow should run on every order.
  • Use Points earned when you want to react to specific Way to Earn campaigns.
  • Use Customer inactive for X days for win-back automations.
  • Use VIP tier changed for tier-based welcome / lifecycle flows.

Conditions (Binary nodes)

A Binary node branches the workflow on a rule. Each has a Yes path and a No path. Stack them to build more complex logic.

What you can branch on

  • Customer attributes (tier, lifetime spend, country, tags)
  • Points balance (greater / less than a threshold)
  • Order attributes (value, item count, contains specific product)
  • Membership status (active / paused / cancelled)
  • Time elapsed since last action

Example branches

  • Tier == Gold or Diamond → send VIP-only email; otherwise send regular email.
  • Cart total > $200 → issue a thank-you coupon; otherwise no action.
  • Has active membership → skip; otherwise upsell.

Best practices

Pick the most specific trigger you can. A narrower trigger means fewer entries and cleaner analytics.
Don’t overload one workflow with conditions. If you have more than 4–5 binary nodes, split into two workflows.
Always send a test customer through end-to-end before activating.

FAQs

No — one trigger per workflow. Build a second workflow if you need a second trigger.
Yes. Each workflow tracks its own entries independently.
By default, re-entry is blocked. You can override per-workflow.

Build your first workflow

A 10-minute walkthrough from blank canvas to a live workflow.

Triggers & Conditions

Events that start a workflow and rules that branch it.

Action Nodes

Send email, credit / debit points, issue a coupon.

Wait & Exit

Pause execution and end a workflow cleanly.

Partner Nodes

Hand off to Engati or KwikEngage.

Analytics

Track entries, completions and step-level drop-off.

Book a Free Setup Call

Talk to our team for personalised setup help.Time: 30 minutes

Contact Support

Visit our support hub for help articles, live chat and ticket submission.

Browse the Guides

Documentation across loyalty, referrals, memberships and more.

Install Yuko

Add Yuko to your Shopify store from the Shopify App Store.