When you enable the HubSpot integration, you can add LINE actions to your HubSpot workflows. Four actions are available: Send LINE message, Send LINE notification message, Update LINE rich menu, and ID linkage by form submission. This article covers what each one is for, its settings, and what you need to use it.
The four LINE actions you can use
When you add an action to a HubSpot workflow, you can choose from four LINE actions provided by Lumo.
| Action | What it does | Workflows it works in | Requirements |
|---|---|---|---|
| Send LINE message | Sends an Auto Send Message or text you enter to the LINE friend linked to the contact | Contact, deal, ticket, company, and others | HubSpot integration |
| Send LINE notification message | Sends a LINE Notification Message based on a phone number, even to customers who haven't added you as a friend yet | Contact | HubSpot integration and the Enterprise plan. LINE Official Accounts in Japan only |
| Update LINE rich menu | Re-evaluates the Rich Menu of the friend linked to the contact against the display target conditions in Lumo | Contact | HubSpot integration |
| ID linkage by form submission | Finds contacts for the same person by a shared value such as a member ID and merges them into one | Contact | HubSpot integration |
Action names and settings appear in Japanese when HubSpot's display language is Japanese, and in English for any other language.
Use HubSpot workflow actions when you want something that happens in HubSpot to drive LINE. Automation that starts from a reaction on the LINE side, such as a friend add or an incoming message, is built with Lumo Workflows. When you're unsure which to use, tell the Marketing Agent your goal and it will propose how to put it together.
What you need to use the actions
Once the HubSpot integration is complete, the four actions appear in the action list of your HubSpot workflows.
| Requirement | Details |
|---|---|
| HubSpot integration is complete | The integration between Lumo and HubSpot must be set up. The steps are covered in How to Set Up the HubSpot Integration |
| The LINE Official Account is integrated | The LINE Official Account you send from or update must be connected to Lumo and integrated with HubSpot |
| The contact's ID is linked | Send LINE message and Update LINE rich menu target the LINE friend linked to the contact. A contact with no linked friend is neither sent to nor updated. The linkage methods are covered in Link HubSpot Contacts and LINE Friends by ID |
| Plan | Send LINE notification message is available on the Enterprise plan. The other three work on every plan that includes the HubSpot integration |
To set up an action, add an action in the HubSpot workflow editor and choose the LINE action from the list.
Send LINE message
This action sends a LINE message to the LINE friend linked to the contact. You can reach people on LINE from HubSpot triggers such as a form submission or a lifecycle stage change.
Settings
| Setting | Details |
|---|---|
| LINE Official Account | The LINE Official Account to send from. Be sure to choose one when you have several accounts integrated |
| Auto message | Choose from the Auto Send Messages you created in Lumo. The picker shows each message's name and description (or the beginning of the body when the description is empty). When you choose one, Message 1–3 below are not used |
| Message 1–3 | The text to send when you don't choose an Auto Send Message. When you fill in Message 2 and 3, they are sent after Message 1 |
| LINE user ID property | Normally leave this unset |
| List ID (legacy) | A setting from the previous mechanism. Normally not used |
When you want to choose an Auto Send Message, pick the LINE Official Account first. The options that appear depend on the account you chose. To send something other than text, such as an image or a Card Type Message, create it as an Auto Send Message in Lumo beforehand. How to create one is covered in How to Create Auto Send Messages.
Using it in deal and ticket workflows
This action works not only in contact workflows but also in deal, ticket, company, and other workflows. It automatically identifies the contact associated with the record and sends to the friend linked to that contact. If there is no associated contact, nothing is sent.
Checking the send results
When you send an Auto Send Message, you can check who received it and the result under "Recipients" in the Auto Send Message details in Lumo. When the contact has no linked LINE friend, the send fails and stays in the recipient list as a failure.
Send LINE notification message
This action sends a LINE Notification Message based on a phone number, even to customers who haven't added you as a friend yet. You can deliver important transactional updates, such as a shipping notice, from a HubSpot workflow.
What you need to use it
| Requirement | Details |
|---|---|
| Plan | Available on the Enterprise plan |
| Region | Available for LINE Official Accounts in Japan |
| Purpose | A LINE Notification Message is a mechanism reserved for transactional notifications that pass LY Corporation's review. It can't be used for advertising or promotions |
| What to send | Prepare an Auto Send Message built with a LINE Notification Message in Lumo. The Auto Send Message consists of a single LINE Notification Message only |
How to create a LINE Notification Message and its restrictions are covered in LINE Notification Message.
Settings
| Setting | Details |
|---|---|
| Phone number (recipient) | Choose the contact property that holds the recipient's phone number |
| LINE Official Account | The LINE Official Account to send from |
| Auto message | Choose the Auto Send Message built with a LINE Notification Message. This action requires an Auto Send Message |
| Message 1–3 | Not used in this action |
| Country code | When the phone number starts with 0, the leading 0 is replaced with the country code you choose. For Japanese numbers, choose "Japan (+81)" |
Checking the send results
You can check who received it and the result under "Recipients" in the Auto Send Message details. For recipients who aren't LINE friends, the recipient cell reads "Notification recipient".
Update LINE rich menu
This action re-evaluates the Rich Menu of the LINE friend linked to the contact against the display target conditions in Lumo and applies the result. Use it when you want a menu switch to take effect right away at a moment you decide on the HubSpot side.
Settings
| Setting | Details |
|---|---|
| LINE Official Account | The LINE Official Account whose Rich Menu to update |
| LINE user ID property | Normally leave this unset |
How it works
You don't specify which menu to show in this action. It evaluates the display targets set on your Rich Menus in Lumo (Segment, period, day of week, and priority) and applies the menu whose conditions match to the friend. The evaluation uses the HubSpot data already synced to Lumo. When the contact has no linked LINE friend, nothing is updated.
How it relates to targeting by Segment
The targeting conditions are set on the Rich Menu side in Lumo; this action's role is to tell Lumo from the HubSpot side when to re-run the evaluation. When a Rich Menu in Lumo has a HubSpot segment (list) as a display target, a sync every 15 minutes picks up membership changes and updates the assignments right after any change. On top of that, all assignments are reviewed every hour. Use this action when you want to re-evaluate a single contact within the flow of a workflow instead of waiting for that automatic update. How to set display targets is covered in How to Create and Apply a Rich Menu.
ID linkage by form submission
This action uses a shared value such as a member ID as the key to find another contact for the same person and merge the two into one. When a contact created as a LINE friend and a contact created by a form submission or member registration exist separately, you can complete the ID linkage in one go.
Settings
| Setting | Details |
|---|---|
| Internal name of the search key property | Enter the internal name of the property whose value, on the contact enrolled in the workflow, serves as the search key (for example, member_id) |
| Internal name of the target property | Enter the internal name of the property on other contacts to search for the search key value (for example, member_id) |
| Primary contact after merge | The contact to keep after the merge. Choose from "System default", "Enrolled contact", and "Found contact" |
For the two properties, type the internal name as text, not the property's value. If you insert a property value (token) from the data panel, the value goes in and the search doesn't work. Email address and phone number can't be used as the target property.
How it works
| Situation | What happens |
|---|---|
| Another contact with the same value is found | The two contacts are merged in HubSpot. Which one is kept follows "Primary contact after merge"; with the system default, Lumo decides. After the merge, the LINE friend is tied to the contact that remains |
| No contact is found | The search key value is written to the target property of the contact enrolled in the workflow, ready to match when a contact with the same value is registered later |
| The search key value is empty | Nothing happens, and the action ends as a failure |
When the ID linkage is established, the "Identity Linked" trigger of a Lumo Workflow fires. Choose "HubSpot workflow ID linking action" as the route, and you can automate a thank-you or a perk for just the friends linked through this route. The trigger settings are covered in Trigger Types and How to Set Them Up.
Use cases
Here is an example of tying LINE friends to existing customer contacts by the member ID from your membership site.
- Send your LINE friends the URL of a HubSpot form where they enter their member ID
- When a friend submits the form, the workflow runs for that contact
- The action finds the existing customer contact with the same member ID and merges the two into one
- The LINE friend is tied to the existing customer contact and can now be used in segmented broadcasts and workflows that draw on the HubSpot customer data
When things don't work
When an action fails, check the link between the contact and the LINE friend, the LINE Official Account you chose, and the required settings.
| Symptom | What to check |
|---|---|
| The LINE message doesn't arrive | Whether a LINE friend is linked to the contact (whether the ID is linked). Check the result under "Recipients" in the Auto Send Message details |
| Sending from a deal or ticket workflow doesn't work | Whether a contact is associated with the record |
| The LINE Notification Message can't be sent | Whether you chose an Auto Send Message, whether the phone number property has a value, whether you're on the Enterprise plan, and whether the LINE Official Account is in Japan |
| The Rich Menu doesn't switch | Whether a LINE friend is linked to the contact, and whether a menu matches the display target conditions. When the condition is a HubSpot segment (list), membership changes reach Lumo only after the 15-minute sync |
| The ID linkage action fails | Whether you entered internal names in the two properties (not value tokens), whether the search key property has a value, and whether you used email address or phone number as the target property |
| The LINE actions don't appear in the action list | Whether the HubSpot integration is complete and whether the Lumo app is installed in HubSpot |
Related articles
These articles are worth checking alongside the LINE actions for HubSpot workflows.
- How to Set Up the HubSpot Integration — Steps to set up the integration
- What You Can Do with the HubSpot Integration — Overview of the integration's features
- Link HubSpot Contacts and LINE Friends by ID — How to link IDs
- How to Create Auto Send Messages — How to create the Auto Send Messages the actions send
- LINE Notification Message — How to create a LINE Notification Message and its restrictions
- How to Create and Apply a Rich Menu — Setting display targets (targeting)
- Trigger Types and How to Set Them Up — Setting up the Identity Linked trigger