A trigger is the event that starts a Workflow. When something happens — such as someone adding you as a friend or sending a specific keyword — the trigger kicks off the automated response you configured. Lumo supports 13 trigger types, each with its own settings to match your use case.
For the Workflow as a whole, just tell Marketing Agent your goal and it will propose a structure. If you say something like "I want to send a greeting when someone adds me as a friend," it prepares a draft Workflow that includes the right trigger. If you prefer to choose and fine-tune triggers yourself, use the settings for each trigger below as a reference.
Trigger types
Lumo Workflows can start from 13 different triggers. The conditions that fire each one and their main uses are as follows.
| Trigger | When it fires | Main uses |
|---|---|---|
| Friend Added | When someone adds you as a friend | Greeting message, first-time survey |
| Message Received | When a friend sends you a message | Keyword replies, automatic answers to common questions |
| Postback Received | When a Rich Menu or button is tapped | Responding to menu actions, processing selections |
| QR Code Scanned | When a specified QR Code is scanned | Sending information during visits or events |
| Video Completed | When a tracked video is watched all the way through | Follow-up after viewing |
| Blocked | When the account is blocked | Post-block processing, recording to external services |
| Cart Abandoned | When a purchase is not completed after checkout | Cart abandonment follow-up |
| Restock | When a previously out-of-stock product is back in stock | Restock notifications |
| Restock (Amp) | When Amp Back in Stock notifies a subscriber of a restock | LINE delivery of restock notifications |
| Purchase Completed | When a purchase is confirmed | Post-purchase thank-you, coupon distribution |
| Shipment Completed | When the shipping status is updated | Shipping notifications, tracking information |
| Browsing Reminder | When a set time passes after a product is viewed | Reminders about viewed products |
| Identity Linked | When an identity link with an external service is established | Thanking people for linking, introducing member perks |
Five of these — Cart Abandoned, Restock, Purchase Completed, Shipment Completed, and Browsing Reminder — are triggers for e-commerce sites and are available when you have set up the Shopify integration. Restock (Amp) requires an integration with the Amp Back in Stock app. Identity Linked doesn't depend on one particular integration — you can start from an identity link made through any route, including QR Codes and the API.
Friend Added trigger
The Friend Added trigger fires the moment someone adds you as a friend. It is the starting point when you want to automatically send a greeting or a first-time introduction.
Settings
| Setting | Description |
|---|---|
| Trigger routes (type) | Choose which friend-add routes fire the trigger, by type. You can select multiple types: QR code (friend add link), Storefront CTA (website friend-add CTA), Klaviyo form submission, Shopify customer account, LINE-native (OA QR, search, and so on), and Message first. If none are selected, every route triggers |
| QR codes (routes) that trigger | Fires only for friends added through the selected QR codes (friend add links). Website friend-add CTAs are selectable as QR codes too |
| Trigger page URL (contains) | Fires only when the page the friend add started on contains one of the strings you specify. You can enter multiple strings separated by commas |
| Exclude QR code origin | When ON, this Workflow doesn't fire for friends who were added via a QR Code |
When you combine the route type, QR code, and page URL conditions, only friend adds that match all of them fire the trigger. For example, set the route type to the website friend-add CTA and require the URL to contain /pages/spring, and the Workflow reaches only friends added through the CTA on that campaign page.
When to use "Exclude QR code origin"
When someone scans a QR Code and adds you as a friend, two triggers fire at the same time: Friend Added and QR Code Scanned. If both Workflows are set to send messages, the same friend receives duplicate, similar messages.
When you turn ON "Exclude QR code origin", this Workflow stops firing for friends added via a QR Code. Only the QR Code Scanned trigger's Workflow runs, which prevents duplicate greetings. It has no effect on friends added through routes other than QR Codes, such as search or a button.
Use cases
- Send a greeting message
- Deliver a self-introduction or service overview
- Run a first-time survey to classify friends
- Leave QR Code add-friends to the QR Code Scanned trigger to prevent duplicate greetings
Message Received trigger
The Message Received trigger fires when a friend sends you a message. By setting keywords, you can make it respond only to messages with specific content.
Settings
| Setting | Description |
|---|---|
| Keywords | Enter the keywords to respond to. You can register multiple keywords |
| Match type | Choose how the keyword and message must match |
| Update unanswered property | When ON, the "LINE Last Reply Message" and "LINE Unanswered" properties on the HubSpot contact are updated every time the trigger fires. Use it when you manage follow-ups for unanswered friends on the HubSpot side |
Match types
The match type determines what kind of match between the keyword and the message causes the trigger to fire. The examples below use the keyword "pricing."
| Match type | Firing condition | Example (keyword: "pricing") |
|---|---|---|
| equals | The entire message exactly matches the keyword | "pricing" → fires / "tell me the pricing" → doesn't fire |
| contains | The keyword appears somewhere in the message | "pricing" and "tell me the pricing" → both fire |
| starts with | The message starts with the keyword | "pricing details" → fires / "monthly pricing" → doesn't fire |
| ends with | The message ends with the keyword | "monthly pricing" → fires / "pricing details" → doesn't fire |
Use cases
- Automatically reply to common questions for keywords such as "pricing" or "booking"
- Launch Customer Agent for specific keywords
Postback Received trigger
The Postback Received trigger fires when a button in a Rich Menu or a message is tapped. Depending on which button was tapped, you can connect it to the next action.
Settings
| Setting | Description |
|---|---|
| Postback Data | Specify the value to respond to. If left empty, all taps are included |
| Match type | Choose how to match the specified value (equals / contains / starts with / ends with) |
Use cases
- Send a message based on which Rich Menu button was tapped
- Process responses to multiple-choice surveys
QR Code Scanned trigger
The QR Code Scan trigger fires when a specific QR Code created in Lumo is scanned. You can serve different information depending on where the code is posted.
Settings
| Setting | Description |
|---|---|
| QR Code | Choose the QR Code to respond to. You must first select the target LINE Official Account |
Use cases
- Post a QR Code at a store or event venue and automatically deliver information to people who scan it
- Send different campaign information for each QR Code
Video Completed trigger
The Video View Completed trigger fires when a friend watches a tracked video all the way through. You can use finishing the video as the starting point for the next action.
Settings
| Setting | Description |
|---|---|
| Tracking ID | Specify the tracking ID set on the target video |
Use cases
- Give a coupon to friends who finish watching a product introduction video
- Guide friends to the next step after they watch educational content
Blocked trigger
The Block trigger fires when the account is blocked. You can automate recording and post-processing when a block occurs.
Settings
It fires automatically when you are blocked, so no special settings are needed.
Use cases
- Record information about friends who blocked you to an external service
- Update data in an integrated external service
Cart Abandoned trigger
The Cart Abandoned trigger is available when you have set up the Shopify integration. It fires for friends who started checkout but didn't complete the purchase.
Settings
| Setting | Description |
|---|---|
| Abandonment Detection Time | Set how many hours after checkout to consider it a cart abandonment |
Use cases
- Send a reminder message to friends who abandoned their cart
- Distribute a coupon to encourage the purchase
Restock trigger
The Restock trigger is available when you have set up the Shopify integration. It fires when a previously out-of-stock product is back in stock.
Settings
| Setting | Description |
|---|---|
| Target Product | Choose whether to target all products or specific products |
Use cases
- Send a notification to friends waiting for a restock
- Deliver information about the restocked product
Restock (Amp) trigger
The Restock (Amp) trigger is available when you have set up an integration with the Amp Back in Stock app. It fires the moment Amp notifies a subscriber of a restock, so you can run a Workflow for the corresponding friend.
Prerequisite
You need an integration with the Amp Back in Stock app. Register your Amp API key in the Shopify integration settings, and set the URL that is issued as the Webhook in the Amp app.
Use cases
- Deliver restock notifications over LINE
- Present restocked products in a product carousel (combined with the auto-send message action)
Purchase Completed trigger
The Purchase Completed trigger is available when you have set up the Shopify integration. It fires when a friend completes a purchase — only for customers whose Shopify customer record is linked to their LINE friend (ID linked). It doesn't fire for guest orders, which carry no customer record.
Settings
| Setting | Description |
|---|---|
| Purchase Type | Choose from All Purchases / First Purchase Only / Contains Specific Product |
| Target Products | When you choose "Contains Specific Product" for the purchase type, specify the target products |
Use cases
- Send a thank-you message or coupon after a purchase
- Update Friend Tags or data at an integrated destination
Shipment Completed trigger
The Shipment Completed trigger is available when you have set up the Shopify integration. It fires when the shipping status of an order is updated. It fires only for customers whose Shopify customer record is linked to their LINE friend (ID linked), and doesn't fire for guest orders, which carry no customer record.
Settings
| Setting | Description |
|---|---|
| Shipment Status | Choose from Any / Fully Shipped / Partially Shipped |
Use cases
- Send a shipping notification
- Provide the estimated delivery date or tracking information
Browsing Reminder trigger
The Browsing Reminder trigger is available when you have set up the Shopify integration. It fires when a friend who viewed a product page doesn't make a purchase within a set time.
Settings
| Setting | Description |
|---|---|
| Reminder Timing | Set how many hours after viewing to send the reminder |
| Target Product | Choose whether to target all products or specific products |
Use cases
- Send a reminder about the viewed product
- Deliver a coupon related to the viewed product
Identity Linked trigger
The Identity Linked trigger fires when an identity link between a friend and an external service is established. You can catch the moment customer data in Shopify or HubSpot connects to a LINE friend, and deliver a thank-you or a perk right away.
Settings
| Setting | Description |
|---|---|
| ID linking routes to trigger on | Choose the linking routes you want to fire on. You can select multiple routes; if none are selected, every route triggers |
| QR codes (routes) that trigger | Fires only for identity links made through the selected QR codes (friend add links). Combined with the route selection, both must match |
| Trigger page URL (contains) | Fires only when the page the identity link started on contains one of the strings you specify. You can enter multiple strings separated by commas |
Routes you can choose
| Route | When it fires |
|---|---|
| QR code (friend add link) | When an identity link is established through a QR Code's friend add link. Scanning alone doesn't fire it — it fires only when the link is established |
| Storefront CTA (website friend-add CTA) | When an identity link is established through a friend-add CTA placed on your website |
| Klaviyo form submission | When a Klaviyo form submission leads to an identity link |
| Shopify customer account | When an identity link is established through a customer account, such as the LINE linking button in Shopify |
| API | When an identity link is established using the Public API |
| HubSpot workflow identify action | When the identity link action in a HubSpot workflow establishes a link |
| Klaviyo flow identity link | When a Klaviyo flow leads to an identity link |
Cases where it doesn't fire
It fires only when an identity link is newly established, or when a link is switched over to a different ID. It doesn't fire in these cases.
- When an already linked friend links again to the same destination with the same details (duplicate linking)
- When links are created by a bulk operation, such as an ID linking import or a scheduled data sync
Watch out for firing alongside other triggers
When a friend is added and linked through a QR Code at the same time, the Friend Added, QR Code Scanned, and Identity Linked triggers can all fire at once. If each of those Workflows is set to send a message, the same friend receives duplicate, similar messages. Keep your linking thank-you in just one of the triggers.
Use cases
- Send a thank-you message and member perks to friends who finished linking
- Update tags or properties on linking, and use them in later broadcasts
Trigger priority
You can set a priority for the Message Received trigger. When multiple triggers could respond to the same message, the priority controls which one runs.
The lower the number, the higher the priority. When a higher-priority trigger matches, triggers with a lower priority don't run. Triggers with the same priority run in parallel.
Only Workflows that can actually run line up for the priority comparison. A Workflow ruled out by the condition branch right after the trigger, or one still within the window that holds off a repeat run for the same friend, drops out of the running. A Workflow that doesn't match its conditions will never stop another one just because it has a higher priority.
When the same trigger overlaps
When another Workflow has a trigger with the same conditions, the editor tells you in three places. That way you notice before the priority comparison quietly stops one of them from running.
| Where you see it | What it looks like |
|---|---|
| Trigger node | The warning "Another trigger with the same conditions exists" is attached |
| Settings panel | The other Workflows line up under "Workflows with the same trigger". Click one to open that trigger and check it |
| Start using dialog | Under "Duplicate triggers detected", it tells you whether both will run or whether priority means only one will |
You can still start using the Workflow when the warning shows. If you lined up the same trigger on purpose, go ahead.
The search covers every Workflow except archived ones, drafts included. Workflows are only compared with each other when they use the same LINE Official Account. If one Workflow has the same trigger more than once inside it, you get the same warning.
Repeat suppression
"Repeat suppression" stops a Workflow from running over and over for the same friend. It keeps the same content from arriving twice when someone hammers a keyword or the same message comes in more than once.
| Setting | Description |
|---|---|
| Repeat suppression | Turn it on and the Workflow won't run again for the same friend within the time you set. You set the suppression window in minutes (1 to 1440 minutes, 2 minutes by default) |
While suppression is in effect, the Workflow also drops out of the trigger priority comparison. If another Workflow is set to respond to the same message, that one runs instead.
Specifying the period and time of day for the Message Received trigger
You can add conditions for the period, time of day, and days of the week when the Message Received trigger fires. This is useful for serving responses differently, such as "respond automatically only during business hours on weekdays."
| Setting | Description |
|---|---|
| Period | Specify the start and end dates during which the trigger is enabled |
| Time of day | Specify the time of day during which the trigger is enabled, in 24-hour notation. Choosing 24:00 as the end time keeps it enabled through the end of the day |
| Days of the week | Specify the days of the week on which the trigger is enabled |
The period, time of day, and day of the week are all judged against the "Time zone" in your workspace settings. The scheduled time for delay actions and the date variables you insert into messages use the same basis. If you run Lumo from an overseas office, check your workspace time zone first.
HubSpot property updated triggers you set up before
HubSpot Property Updated triggers you set up before still work exactly as they did. They are no longer available to choose as the trigger for a new Workflow.