How to Broadcast LINE Messages to Teams from a Workflow

 How to Broadcast LINE Messages to Teams from a Workflow

Summary

  • The LINE Messaging API supports broadcast to all friends, push to one user, multicast to a list, and narrowcast to a segment; billing is counted per recipient, not per message object.
  • Use a long-lived channel access token for simple scheduled workflows, and store it in a secure credential store rather than plain text.
  • Build the automation in Jinba Flow by adding an HTTP Request node for POST /v2/bot/message/broadcast, then add a Schedule or event-driven trigger for unattended sends.
  • Verify delivery with GET /v2/bot/message/delivery/broadcast, handle 429 errors with exponential backoff, and review the October 1, 2026 LINE fee changes before FY2026 budgeting.
  • Jinba Flow lets teams automate LINE broadcasts and push messages with no code and 100+ integrations.

Note: This guide targets teams using the LINE Messaging API for internal communications, a common pattern in Japan where LINE is the dominant team messaging channel.

For Japanese organizations that use LINE for internal announcements, broadcast sending is typically a manual process. Existing guides on the topic begin with Google Apps Script or Node.js, which presents a barrier for teams without a development background. This guide covers a no-code/low-code alternative using Jinba Flow, a workflow builder with 100+ integrations that runs on deterministic, rule-based execution.

The result is a working line broadcast message automation covering credential setup, broadcast and push sending, audience data retrieval, and scheduled or event-based triggering.


What the LINE Messaging API offers internal teams

The LINE Messaging API is most commonly described as a customer engagement tool, but its sending methods map cleanly onto internal team communication patterns. The mechanism is the same: team members follow a dedicated LINE Official Account, and the account sends messages to them.

The API provides five outbound sending methods:

  • Broadcast - sends to every friend of the account at once; the right choice for all-team announcements
  • Push - sends to a single user ID; used for direct, individual messages
  • Multicast - sends to a specified list of user IDs in one call
  • Narrowcast - sends to a pre-defined audience segment, such as "on-call engineers" or a regional group
  • Reply - responds to an inbound webhook event; not relevant for proactive announcements

Three terms appear throughout this guide:

  • Channel access token - the credential placed in the Authorization: Bearer header of every API request
  • Message object - the JSON structure that defines message content (type, text, media, etc.)
  • Webhook URL - the endpoint that receives inbound events from LINE, required for reply-type interactions

Part 1: Setting up your LINE channel and credentials

Step 1: Create a provider and Messaging API channel.

Go to the LINE Developers Console and create a provider. Inside that provider, create a new channel and select Messaging API as the channel type. This is the account that will send all workflow messages.

Step 2: Locate your Channel Secret and Channel Access Token.

These two credentials are distinct and serve different purposes:

  • Channel Secret - used to validate webhook signatures and to issue tokens via the OAuth endpoints. It does not appear in message-sending requests.
  • Channel Access Token - the credential used in every message-sending API call. Place it in the Authorization: Bearer {token} header.

Step 3: Choose the right token type.

The LINE documentation defines four token types. For workflow automation, three are relevant:

Token type

Validity

Suitable for

Long-lived

Indefinite

Getting started; simple, low-frequency workflows

Stateless

15 minutes

Short workflow steps that generate a fresh token per execution; cannot be revoked once issued

v2.1

Up to 30 days (user-defined)

Long-running schedulers; issued via JWT signed with a private key; most secure option

For most teams starting out, a long-lived token is the simplest path. Issue it from the Messaging API tab inside the channel settings in the LINE Developers Console. Store the token in the secure credentials store of your workflow tool, never in a plain text field.

LINE provides a revocation endpoint at POST /oauth2/v2.1/revoke for any token suspected of compromise.

Part 2: Building the broadcast workflow in Jinba Flow

Action 1: Broadcast to the entire team

The broadcast endpoint sends a single message to every user who has added the LINE Official Account as a friend.

Endpoint: POST https://api.line.me/v2/bot/message/broadcast

Required headers:

Content-Type: application/json
Authorization: Bearer {your_channel_access_token}

Request body:

{
"messages": [
{
"type": "text",
"text": "Team reminder: the weekly all-hands meeting starts in 15 minutes."
}
]
}

In Jinba Flow, add an HTTP Request node, set the method to POST, paste the endpoint, and add both headers. Paste the JSON body above into the body field.

One common issue when connecting LINE to workflow tools is JSON validation errors on the request body. If the tool requires the body to be passed as a string rather than a raw object, wrap it using a JSON.stringify expression:

JSON.stringify({
messages: [{ type: "text", text: "Your message here" }]
})

This resolves the validation error without changing the API call itself.

Action 2: Push a message to a specific team member

A push message targets a single user by their LINE user ID. The body structure adds a to field.

Endpoint: POST https://api.line.me/v2/bot/message/push

Request body:

{
"to": "Uxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"messages": [
{
"type": "text",
"text": "Hi Alex, can you review the Q3 report draft before the 3pm call?"
}
]
}

To retrieve a user's ID programmatically, call GET /v2/bot/profile/{userId} or retrieve it from a webhook event the user previously triggered.

Action 3: Narrowcast to a team segment

Narrowcast sends to a pre-defined audience group, for example "design team" or "on-call rotation."

The prerequisite is creating an audience group first. Upload a list of user IDs via:

POST /v2/bot/audienceGroup/upload

Once the group exists, reference its ID in the narrowcast request body. Track delivery progress via:

GET /v2/bot/message/progress/narrowcast


Part 3: Verifying delivery and monitoring usage

A working broadcast workflow includes a verification step. The LINE Messaging API reference exposes a full set of post-send endpoints:

  • GET /v2/bot/message/delivery/broadcast - returns the number of messages delivered for a broadcast on a given date
  • GET /v2/bot/message/quota - shows the monthly message limit on the current plan
  • GET /v2/bot/message/quota/consumption - shows how much of the quota has been used in the current period
  • GET /v2/bot/info - returns the current friend count; useful for confirming audience size before a large broadcast

Rate limits and error handling. Exceeding the API's rate limit returns a 429 Too Many Requests status code. Configure the workflow to handle this with an exponential backoff and retry, rather than re-sending immediately. Repeated instant retries will continue to hit the limit. Check the current per-endpoint limits in the official documentation.

Part 4: Scheduling and triggering the workflow

A broadcast that requires manual initiation offers limited improvement over manual sending. Two trigger patterns complete the automation.

Scheduled trigger (cron). In Jinba Flow, add a Schedule trigger node and configure it with a cron expression. For a Monday morning kickoff message, set it to fire every Monday at 09:00 JST. The trigger node runs the broadcast step automatically without any manual action.

Event-driven trigger. Connect the LINE broadcast step to another system. Practical examples:

  • A new row in a Google Sheet (for example, a new incident report) triggers a push message to the on-call engineer
  • A status change in a project management tool triggers a narrowcast to the relevant team segment
  • A form submission triggers a confirmation push to the submitter's LINE account

Jinba Flow supports all of these as upstream trigger steps, meaning the LINE message action is downstream of an event from another connected service.


Cost considerations for teams in Japan

LINE message billing is counted per recipient, not per message object. A single API call that sends four message objects to a 10-person friend list counts as 10 messages towards the monthly quota, not 4.

Practical implications:

  • Keeping the friend list current directly affects cost. Messages sent to user IDs that are invalid or have blocked the account are not counted, so removing former employees reduces waste.
  • Multicast and narrowcast to smaller lists consume fewer messages than a full broadcast, which is relevant when only a subset of the team needs a given announcement.

LINE has announced that additional-message fees for LINE Official Accounts in Japan will be revised effective October 1, 2026. Teams planning automated communication budgets for FY2026 should review the official announcement before finalising message volume estimates.


Next steps

The workflow covered here handles the full sending cycle: credential setup, broadcast to all team members, push to individuals, narrowcast to segments, delivery verification, and scheduled or event-based triggering. Each step is a discrete node in Jinba Flow, replaceable or reorderable as requirements change.

The immediate next actions:

  1. Create the LINE Official Account and Messaging API channel in the LINE Developers Console
  2. Issue a channel access token and store it in the Jinba Flow credentials store
  3. Build a single HTTP Request node with the broadcast endpoint and confirm delivery via GET /v2/bot/message/delivery/broadcast
  4. Add a Schedule trigger node to run the broadcast automatically
  5. Review message quota consumption against the revised pricing timeline before October 2026

Teams that complete these steps move from a manual, error-prone process to a durable, auditable line broadcast message automation that any team member can maintain without writing code.


Frequently asked questions

How do I automate LINE broadcast messages without writing code?

The implementation requires a workflow automation tool with a schedule trigger and a generic HTTP Request node pointed at the LINE Messaging API broadcast endpoint. The setup has three components: a LINE Official Account with a Messaging API channel, a channel access token stored as a credential, and a POST request to https://api.line.me/v2/bot/message/broadcast with the token in an Authorization: Bearer header. In a tool like Jinba Flow, this is a Schedule trigger node wired to an HTTP Request node, with no Google Apps Script or server code to maintain. Any team member can edit the message text or the schedule without touching the underlying API call.

What is the difference between broadcast, push, multicast, and narrowcast in the LINE Messaging API?

Broadcast sends to every friend of the account at once, push sends to one user ID, multicast sends to a supplied list of user IDs in a single call, and narrowcast sends to a pre-defined audience segment. Method choice affects cost, because billing is counted per recipient rather than per call. Broadcast suits all-team announcements such as a weekly all-hands reminder, push suits one-to-one messages such as a review request to a named colleague, multicast applies when the exact user IDs are already known, and narrowcast covers standing segments such as "on-call engineers" or "design team." Reply messages, the fifth method, only respond to inbound webhook events and are not usable for proactive announcements.

How do I get a channel access token for the LINE Messaging API?

Issue it from the Messaging API tab inside your channel settings in the LINE Developers Console. The channel access token is separate from the Channel Secret: the secret validates webhook signatures and issues tokens via OAuth, while the access token is what appears in the Authorization: Bearer {token} header of every message-sending request. Once issued, the token belongs in the workflow tool's secure credential store rather than a plain text field or a spreadsheet. If a token is ever exposed, revoke it with POST /oauth2/v2.1/revoke and issue a replacement.

Which channel access token type should I use for a scheduled LINE workflow?

For most internal teams starting out, a long-lived token is the simplest and correct choice. It has indefinite validity and requires no token-refresh logic, which suits low-frequency announcements and pilots. Two exceptions apply: a stateless token (15-minute validity) suits short workflow steps that generate a fresh token per execution, accepting that it cannot be revoked once issued; and a v2.1 token, issued via a JWT signed with a private key and valid for up to 30 days, suits long-running schedulers where security requirements are higher.

Why does my LINE API call fail with a JSON validation error?

The request body is likely being sent as a raw object when the tool expects a string. Wrap the JSON in a JSON.stringify expression so the payload is serialized before it leaves the workflow: JSON.stringify({ messages: [{ type: "text", text: "Your message here" }] }). This resolves the validation error without changing any part of the API call: the endpoint, headers, and message structure all stay the same. It is the most common issue when connecting the LINE Messaging API to a low-code HTTP connector.

How much does it cost to send LINE messages to an internal team?

LINE message billing is counted per recipient, not per message object. If one API call sends four message objects to a 10-person friend list, that consumes 10 messages from the monthly quota, not 4. Two practical implications follow: keep the friend list current, because messages to invalid user IDs or users who have blocked the account are not counted, so removing former employees reduces waste; and use multicast or narrowcast over a full broadcast when only part of the team needs a given announcement. LINE has announced that additional-message fees for Official Accounts in Japan will be revised effective October 1, 2026, so teams planning FY2026 volumes should review the official announcement before finalising estimates.

How do I check whether a LINE broadcast was actually delivered?

GET /v2/bot/message/delivery/broadcast with the target date returns the number of messages delivered for that broadcast. Paired with GET /v2/bot/message/quota and GET /v2/bot/message/quota/consumption, it shows the monthly message limit and how much of it the send consumed, and GET /v2/bot/info confirms the friend count before a large broadcast. The verification step belongs in the workflow itself, as a node that runs immediately after the send, so a failed or partial delivery surfaces without manual checks in the console.

What should I do when the LINE Messaging API returns 429 Too Many Requests?

A 429 response requires exponential backoff and retry rather than an immediate re-send. The code indicates the per-endpoint rate limit has been exceeded, and repeated instant retries will keep hitting the same limit and consume workflow executions. Configure the HTTP Request node to wait progressively longer between attempts, and cap the number of retries so a persistent failure escalates to an operator rather than looping indefinitely. Check the current per-endpoint limits in the official Messaging API reference before sizing batch sends.

How do I send an announcement to only part of the team?

Narrowcast with an audience group reaches part of the team rather than the full friend list. The group is created first by uploading a list of user IDs to POST /v2/bot/audienceGroup/upload, and the narrowcast request body then references that group ID. Delivery progress is tracked with GET /v2/bot/message/progress/narrowcast. Where the exact user IDs are already known and the list is small, multicast is simpler: it sends to a supplied list in one call and needs no pre-built audience group.

How do I find a team member's LINE user ID?

Capture it from a webhook event the user triggered (a follow or message event delivered to the webhook URL), or read it from an existing audience list. GET /v2/bot/profile/{userId} returns that user's profile details and confirms the ID is valid before a push is sent. Message-sending calls accept only the U-prefixed user ID, not a display name or email address, so IDs are best stored at the point of capture and reused rather than resolved by name later.

Build your way.

The AI layer for your entire organization.

Get Started