Action Types and How to Configure Them

A Workflow action is the processing that runs after a trigger fires. You can combine actions such as sending messages, asking questions, and branching by condition to design your automation flow.

What Are Actions?

Actions are the individual processing steps that run in order after a trigger fires. You connect multiple actions together to build a complete automated response.

In the settings panel, actions are organized into the following three categories.

You can leave the design of the entire Workflow to the Marketing Agent. Just tell it your goal, such as "Send a coupon three days after someone adds us as a friend," and the agent prepares a draft with the necessary actions lined up. If you want to fine-tune things yourself, add nodes in the editor and configure each action.

Send Message

This action sends a message such as text or an image directly to your friends. Use it when you want to send fixed content on the spot, such as a greeting or an announcement.

You can also configure multiple messages together and send them all at once.

Auto Send Message

This action calls up an Auto Send Message item you created in advance and sends it. Instead of typing frequently used guidance every time, you can reuse it as a template.

From the settings panel, you can move to the screen for reviewing or creating Auto Send Messages. If you do not yet have the content you want to send, create the Auto Send Message item first and then select it.

Question

This action sends a question to your friends, then collects and saves their answers. Use it for surveys or to gather attribute information, and the answers can be stored as tags or as properties in an integrated service.

Answer Format

Choose from two ways of receiving answers.

Answer Button Type

When you have friends answer with choices, you can choose how the choices are displayed on LINE.

Due to LINE's specifications, there are limits on the number of choices and the character count of labels. Anything over the limit is truncated when sent, so adjust your settings to stay within the guidelines shown in the settings panel.

Input Validation (for Free Input)

For free input, you can validate the format of the content you accept in advance. You can display an error message for answers that do not match the format.

Where Answers Are Saved

Collected answers can be saved to one of the following.

What you assign here is a Friend Tag. It is a different concept from a broadcast Segment, so please be careful not to confuse them.

Condition Branch

This action splits the flow into two based on a condition. You can run different actions for friends who match the condition (True) and friends who do not (False).

Condition Type

Choose the condition used for the evaluation.

The tag condition uses Friend Tags for evaluation, while the Segment condition uses broadcast Segments. Tags and Segments are different concepts, so choose the one that suits your purpose.

Property Condition Operators

For property conditions, you specify how values are compared using operators.

Configuring the Random Condition

The random condition assigns friends who reach this point into two groups, True and False, at a specified ratio. Use it when you want to split by probability, such as for a lottery or an A/B Test.

Splitting Into Three or More Groups With the Random Condition

A single random condition node splits into two options, True and False, but you can achieve a split into three or more groups by connecting condition branches in sequence. The trick is to connect the next random condition to the False side of each node and raise the ratio little by little.

When splitting into six groups roughly evenly, the guideline for each node's True ratio is as follows.

Using this method, you can run a lottery campaign or deliver different message patterns.

Tag

This action adds a tag to or removes a tag from a friend. You can record an attribute in the middle of a flow and use it for later condition branches or for creating Segments in a Message Broadcast.

What is handled here is a Friend Tag. It is different from the tag you attach to a conversation in the Chat screen or the Segment that narrows down broadcast recipients, so please be careful not to mix them up. If you do not have a tag yet, create the tag first and then select it.

Delay

This action waits for a specified amount of time before the next action. Use it when you want to space out the interval between messages, or when you want to send a reminder after a certain period.

Unenrolling an Individual Friend Who Is in a Delay

You can remove a specific friend who is waiting at a delay node from the Workflow partway through. Use it when a test friend has been enrolled repeatedly, or when you want to stop subsequent broadcasts for a specific friend only.

Unenroll using the following steps.

1. Click the target delay node in the Workflow editor
2. From the Friends in delay list shown in the settings panel, click the trash can icon on the row of the friend you want to remove
3. Click Unenroll in the confirmation dialog

Behavior After Unenrolling

An unenrolled friend is removed from that Workflow's execution.

• Their waiting state is canceled
• Even when the set time arrives, subsequent steps such as sending a message are not executed
• If the same Workflow's trigger fires again, the friend is enrolled in the Workflow once more (the fact that they were previously removed is not carried over)

Notes on Unenrolling

Please keep the following in mind when unenrolling.

• The Friends in delay list shows up to 10 people. If there are more than 10 friends waiting, friends who do not appear in the list cannot be unenrolled from this screen
• Once you unenroll, it cannot be undone
• Even if a friend blocks you on LINE, the Workflow itself keeps progressing. If you want to remove them completely from the Workflow, use this unenrollment

Customer Agent

This action launches an AI agent and starts automated responses with the friend. The Customer Agent answers questions and hands off to an operator as needed.

The Customer Agent node has two branches, True and False. When a friend taps the end button, they proceed to the True branch; when they tap the human handoff button, they proceed to the False branch. You can connect a different action after each branch.

Update Rich Menu

This action switches the Rich Menu displayed to a friend, or removes it. You can show different menus as the flow progresses.

Select the Rich Menu from those already applied to LINE in advance. If there is no synced Rich Menu, apply the Rich Menu to LINE first.

External Service Integration Actions

These actions integrate with HubSpot or Klaviyo to reflect a friend's information in an external service. They are available when an integration is set up.

HubSpot Property Setting

Updates a HubSpot contact property.

HubSpot Workflow Enrollment

Enrolls a contact in a Workflow on the HubSpot side.

Klaviyo Property Setting

Updates a Klaviyo profile property.

Add to Klaviyo List

Adds a profile to a Klaviyo list.

Send Klaviyo Event

Sends a custom event to Klaviyo.

Send Webhook

This is an advanced action for developers that sends data to an external service. Use it when you want to integrate with an internal system or another tool.

Because configuration requires specialized knowledge, set it up while checking the specifications of the integrated service.

Execute Code

This is an advanced action for developers that runs JavaScript code. Use it when you need custom processing that is difficult with the standard actions.

The execution result can be used in subsequent actions. Because specialized knowledge is required, set it up in consultation with your own developers.