Resources · Zapier integration

Loku Zapier integrationAutomate Loku with Zapier.

The Loku Zapier integration gives you 3 triggers, 2 actions and 0 searches. New friends, incoming LINE messages and new reservations can start a Zap, and a Zap can message a friend or change their tags. What it does, what it costs, where it stops.

Beta app Zapier still marks this integration as beta.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Loku Zapier integration actually does

Loku is a marketing platform built on LINE for businesses in Japan: it ties the friends of your official account to reservations, forms and payments. Through Zapier, it works in both directions. Three events in Loku can start a Zap, and two actions let a Zap write back to a friend.

Three results come up again and again. A booking confirmation: New Reservation starts the Zap and Send LINE Message writes to the friend, with the reservation time mapped into the text. A sorted friend list: New Friend fires and Add or Remove Tag labels the newcomer, so later campaigns reach the right people. A shared inbox: New Message hands each incoming LINE message to another tool where the team already reads things.

Now what Zapier does not do here. There is no search, so a Zap cannot look up a friend by name; it relies on a friend chosen in the step or an ID carried by an earlier one. No action creates a reservation, a friend or a tag. The Tag field asks you to select a tag that already exists in Loku. Zapier also lists this integration as beta, which is worth knowing before you build anything critical on it.

If you are still choosing a platform, see our n8n vs Zapier comparison and our Zapier review.

Vocabulary

Zapier words, in plain English

Seven terms come back on this page. Here is each one in a line.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts a Zap. Once the Zap is on, Zapier waits for it: here a new friend, message or reservation.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, like a LINE message or a tag.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and the number on your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it there otherwise.
Connection
Your Loku account linked to Zapier once, then reused by every Loku step in every Zap you build after that.
Cost

What a Loku Zap really costs

Loku is not a premium app, so it runs on the free plan. Its three triggers never cost a task: only an action that goes through is billed.

  • Triggers0 tasks, ever
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A New Friend Zap that adds one tag uses one task per new friend. Put a LINE message after the tag and each friend costs two. An action that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. A filter or a second action makes the Zap multi-step, and that needs a paid plan. The grid below shows how often Zapier checks polling triggers on each plan; it does not apply to Loku, whose three triggers are all instant.

Connect

Connect Loku to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A dialog with a search box appears. You need a Loku account first: Zapier only links to one that already exists.

  2. 02

    Find Loku

    Type Loku in the dialog, pick it from the results, then click Add connection. A new tab opens on the Loku side, where you sign in with the login you already use.

  3. 03

    Grant access

    Sign in, then allow Zapier to reach the account. The connection is stored once and every Loku step reuses it. If the LINE account is run by someone else, check first that your login can see its friends and tags.

First Zap

Your first Zap: confirm each booking over LINE

GoalEach new reservation in Loku sends a LINE message to the friend who booked, with the booking time in the text, so the confirmation leaves without anyone typing it.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Loku as the app and New Reservation as the event, then select the Loku connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you build the next steps on a real reservation instead of a blank one.

  3. 03

    Add a filter if needed

    Optional: add a filter and set the field, the rule and the value, so only the reservations you choose go on. With it, the Zap becomes multi-step and needs a paid plan.

  4. 04

    Write the message

    Add Send LINE Message. In Friend, pick the friend or map a friend ID from an earlier step. In Message Text, write the confirmation and map the reservation time into it.

  5. 05

    Test, then Publish

    Test the action and check that the message arrives on LINE as written. Then click Publish to switch the Zap on; each new reservation now sends its own message.

Triggers

The three Loku triggers

3 events start a Zap when something happens in Loku, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Friend

Instant trigger

In Zapier“Triggers when someone adds your LINE official account as a friend.”

Someone adds your LINE official account as a friend, and this trigger starts the Zap with that new friend in hand, ready to be tagged, greeted or logged elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want every newcomer sorted with a tag as soon as they join, so later messages go to the right segment.
Watch out
a Zap only sees friends added after it is published, so the friends you already have are never picked up.
2

New Message

Instant trigger

In Zapier“Triggers when a friend sends a LINE message to your account.”

Every LINE message a friend sends to your account sets this one off, and the message travels into the Zap so another tool can store it, route it or alert a colleague.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
questions arriving on LINE should also show up where the team already works, without anyone watching the Loku screen.
Watch out
each incoming message is its own run, so a busy chat multiplies the tasks of every action in the Zap.
3

New Reservation

Instant trigger

In Zapier“Triggers when a new reservation is created in Loku.”

A booking created in Loku opens the Zap here, with its details available to map into what follows: a confirmation, a calendar entry, a row in a sheet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a confirmation or a record should follow every booking without anyone copying it by hand.
Watch out
reservations made before the Zap was published never come through; moving the older ones is a separate job.
Actions

The two Loku actions

Loku gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Send LINE Message

Action

In Zapier“Sends a LINE text message to a selected friend in Loku.”

Writes to one friend of your Loku account over LINE. You choose the friend or map their ID from an earlier step, then compose the text, with names or reservation times mapped in.

When to use it
a booking confirmation or a welcome that should reach the friend on LINE right after the trigger.
Watch out
the text is capped at 5,000 characters, mapped fields included.
2

Add or Remove Tag

Action

In Zapier“Adds a tag to or removes a tag from a friend in Loku.”

Puts a tag on a friend, or takes one off, depending on what you set in the required Action field. The friend comes from the list or from an ID mapped from an earlier step.

When to use it
new friends or recent bookers should land in a segment you can message later.
Watch out
the Tag field expects an existing Loku tag, and no Loku action on Zapier creates one.
When it breaks

When a Loku Zap breaks

Zapier attaches no help article and no rate limit to Loku, and lists the integration as beta. Most failures come from how Zapier itself works, plus the required fields of the two actions.

  • Older friends and bookings stay out

    A Zap only reacts to what happens after it is published. Friends, messages and reservations from before never go through it; moving them is a separate job.

  • A Zap that sets itself off

    If a Zap writes into the very place its own trigger watches, it starts itself again and again, and burns through your task count fast.

  • A sudden burst gets held back

    When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold the runs back instead of firing them all.

  • The message is too long

    Message Text accepts up to 5,000 characters. A long template filled with several mapped fields can go past that, so keep the wording tight.

  • The tag does not exist yet

    The Tag field of Add or Remove Tag asks for an existing Loku tag, and no action on Zapier creates one. Set it up in Loku first, then select it in the step.

  • No friend to act on

    Both actions require a friend. If you neither pick one nor map a friend ID from an earlier step, the action has nobody to message or tag.
Need help

Need help automating Loku with Zapier?

A person reads every message.

FAQ

Loku Zapier integration: frequent questions

01Is the Loku Zapier integration free?
Yes. Loku is not a premium app, so it works on Zapier's free plan. That plan gives 100 tasks a month and builds two-step Zaps: one Loku trigger and one action, such as tagging each new friend. Adding a filter or a second action makes the Zap multi-step, and that needs a paid plan. The triggers themselves never cost a task, so a quiet month costs nothing at all, however many friends the Zap is watching.
02How many tasks does a Loku Zap use?
One task per action that succeeds, each time the Zap runs. A Zap that sends one LINE message per reservation uses one task per reservation; one that also adds a tag uses two. Failed actions are not counted, and the three triggers cost nothing. New Message deserves a closer look: every incoming message is a run, so a Zap on a lively chat consumes tasks quickly. With the free plan's 100 tasks a month, a two-step Zap handles 100 runs before it hits the ceiling.
03Do Loku triggers work in real time?
Yes, all three are instant triggers. For New Friend, New Message and New Reservation, the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan. Most Zapier triggers are polling ones, checked on a timer that depends on the plan, but that grid does not apply here: a free account gets the same speed as a paid one. A Zap built on an instant trigger shows a lightning bolt in the editor, and the type cannot be changed from there.
04What do you need to connect Loku to Zapier?
A Loku account, a Zapier account, and access to the LINE account the Zap should work on. In Zapier, open the Apps page, click + Add connection, search for Loku and click Add connection. Sign in to Loku in the tab that opens, then grant Zapier access. The connection is saved once and every Loku step reuses it. If the account is managed by a colleague, your login needs read or write access to the friends and tags the Zap should touch.
05Which tags can Add or Remove Tag use?
Tags that already exist in Loku: the required Tag field asks you to select one of them. The action puts that tag on a friend or takes it off, and neither Loku action creates a tag. So the tag work happens in Loku first, then you come back to the Zap step and select it. The same logic applies to the Friend field, which needs a real friend, chosen from the list or mapped by ID from an earlier step. Without one, the action has nothing to work on and the step cannot do its job.
06What if the Loku operation you need does not exist?
Then Zapier cannot do it for Loku as things stand. The integration offers three triggers and two actions: sending a LINE message, and adding or removing a tag. There is no search, so a Zap cannot look up a friend, and no action creates a reservation or a tag. Anything outside that list has to happen in Loku itself. If the gap blocks a whole workflow, the Hack'celeration team can look at the case and say whether another route is worth building.
07Zapier, Make or n8n for Loku?
It comes down to criteria, not a winner. Zapier has ready Loku triggers and actions, and its instant triggers run at the same speed on every plan, which suits a team that wants a working flow quickly. Its cost grows with every successful action, so a chat-heavy Zap on New Message adds up. Make and n8n are worth checking if you expect many steps per run; whether they offer a ready Loku module is something to verify on their side. Volume, number of steps and who maintains the flow decide.
Same platform

Other docs you might need on this stack.

Browse all integrations