Sending flexible-type LINE notification messages

Flexible-type LINE notification messages deliver reviewed text and layouts by phone number. In Lumo, prepare the approved content in an Auto Send Message and call it through the notification sending action.

For applications, see Applying to use LINE notification messages. To use official predefined content, see Sending template notifications.

Official information checked on September 9, 2026. The steps focus on LINE Official Accounts in Japan.

What you need to use this feature

Complete the LINE notification application and UX review for the intended purposes and content before using flexible notifications.

• An Enterprise plan in Lumo
• An approved LINE Official Account connected to Lumo
• Completed UX review for the flexible notification's purposes and message items
• Access to the approved text, layout, and button destinations
• Recipient phone numbers and the data to merge
• For HubSpot, a connected Lumo integration and access to contact-based workflows

Apply again when adding purposes or message items. Template approval or a history of sending regular Flex Messages doesn't replace this review. Flexible UX guidelines

Understanding the difference from Flex Messages

Flexible type describes how the notification is delivered; Flex Message describes how its content is built.

Creating a Flex Message and choosing a regular sending action doesn't deliver a phone-based notification to non-friends. Select the prepared Auto Send Message in "Send LINE Notification Message" to use the flexible route.

Preparing approved content in an Auto Send Message

Build flexible notifications in an Auto Send Message using the reviewed content.

Marketing Agent can help organize the setup and draft from approved material. Before sending, verify that the result matches the reviewed content.

Manual setup

1. Open "Automation" > "Auto-Send Messages"
2. Click "Create auto-send message"
3. Enter a name that identifies the purpose and type, such as “Reservation confirmation — flexible”
4. Add the reviewed message format; select Flex Message for a Flex layout
5. Enter the approved JSON in the Flex JSON field and set the alternative text
6. Check the preview and click "Save content"

If your approved format is text, enter that text instead. Keep each send within five messages and preserve the reviewed structure. Don't mix the template-type LINE notification message item into this Auto Send Message.

For JSON editing, see Creating Flex Messages and the Flex Message Simulator. Don't add promotional or coupon examples from regular messaging guides to an approved notification.

Checking merged values and destinations

Values that change per send must stay within the reviewed items and purposes.

For reservation notices, merge only permitted details such as the reservation date, number, and venue. Match variables to the source data. Test missing values, long values, and special characters to ensure the text and JSON remain valid.

LINE display names may be unavailable for recipients who haven't added the account. For HubSpot sends, use properties available from the target contact.

Don't place explicitly identifying personal information in the body. Require authentication before displaying personal information at a linked destination. Keep destinations related to the notice and don't add advertising or promotional links. Flexible UX guidelines

Images and other media

The flexible UX guidelines updated September 8, 2026 allow still images under conditions. LINE Developers' technical specifications still say images aren't allowed. Before using images, confirm the applicable conditions and review scope with your representative. Video and audio aren't permitted. Latest UX guidelines, technical specifications

Product carousels are sent as alternative text through the flexible notification route. To preserve an approved card layout, configure it as a Flex Message rather than substituting a product carousel.

Sending from a HubSpot workflow

Use Lumo's phone-based notification action to reach HubSpot contacts who haven't added the account as a friend.

1. Create or edit a contact-based HubSpot workflow
2. Choose a trigger that matches the reviewed purpose, such as reservation or shipment confirmation
3. Add Lumo's LINE notification message action
4. Set the fields below
5. Save with enrollment restricted to test contacts

Don't enter content directly in Message 1–3; an Auto Send Message is required. For repeat notifications, check re-enrollment and conditions that prevent duplicate sends for the same reservation or order.

See LINE actions in HubSpot workflows for shared settings.

Sending from a Lumo Workflow

Lumo Workflows can call an approved Auto Send Message through the notification action.

1. Open the Workflow under "Automation" > "Workflows"
2. Set the sending LINE Official Account and trigger
3. Choose "Send LINE Notification Message"
4. In "Auto-send message", select the approved Flex or text message
5. Check the target customer's stored phone number and save

This route uses the number stored for the Workflow's target customer. It isn't a recipient field for a list containing only phone numbers. For external-service customers who haven't added the account, configure the corresponding notification integration. Creating a Workflow

Testing through the notification action

Test flexible notifications with designated recipients through the actual notification sending action.

The Auto Send Message editor's "Delivery confirmation" for regular Flex or text messages can check appearance. It doesn't validate phone-based flexible notification delivery.

1. Store the test recipient's phone number in the sending system's customer data
2. Enable notification receipt on the test LINE account and unblock the sender
3. Restrict the Workflow to test customers
4. Activate the Auto Send Message and run the notification action
5. Complete SMS verification if LINE requests it
6. Compare the delivered content with the reviewed text and layout; check merged values and destinations
7. Confirm results before configuring regular triggers and re-enrollment

See LINE's receiving flow for consent and verification.

Checking results and tracking limits

For flexible notifications sent from HubSpot, check sent and delivered timestamps in the Auto Send Message's recipient list.

Non-friends appear as "Notification recipient". For Lumo Workflows, check the execution history.

Lumo doesn't provide per-recipient open or click tracking for flexible notification sends. Tracking differs from regular Flex broadcasts and template notifications. Missing click records aren't evidence of failed delivery.

A successful send request doesn't guarantee delivery. Receiving settings and SMS verification can prevent receipt. Technical specifications

When things don't work

Check the sending action, approval, phone number, and content in that order.

If the issue continues, contact support with the Lumo ID, sender, message name, sending time, Workflow name, and error. Don't repeatedly resend the same notification without checking the cause.