Reference · Tools

Line

Send notifications via LINE Notify with optional image uploads and sticker attachments.

Action (binary) Communication v1 Binary data

The Line node sends notifications through LINE Notify, optionally attaching an image — either by URL or uploaded from binary data — and a sticker. A typical build is pushing a build-failure or on-call alert straight to a team's LINE group with a screenshot attached.

Node type
Action (binary)
Parameters
9
Outputs
Output, Error
Credentials
LINE Notify

Line

Send LINE Notify notifications with images and stickers

Overview

The Line tool sends push notifications to LINE users or groups via the LINE Notify API. It supports plain text messages, image attachments (via URL or binary file upload), and LINE sticker attachments. The notification target is determined by the OAuth2 token binding — the token is bound to a specific user/group at authorization time. Note: LINE Notify was officially discontinued on April 1st, 2025.

Category: Communication
Tool Name: line
Version: 1

Appearance: Icon: si-line | Color: #00C300

Node Type

Action (Binary) — handles file/binary data operations

Input / Output

DirectionPort(s)
InputInput
OutputOutput, Error

Credentials

This tool requires LINE Notify credentials. See the Credentials Guide for setup instructions.

Parameters

ParameterTypeRequiredDefaultDescription
MessagestringYesThe notification message text. Max 1000 characters. Supports expressions like {{ $json.text }}.
Image ModeoptionsNononeHow to attach an image to the notification.
Options: none (no image attachment), url (attach image by providing full-size and thumbnail URLs), binary (upload an image from binary data on the input item)
Image Full Size URLstringNoHTTP/HTTPS URL of the full-size image. Maximum 2048x2048px JPEG. Supports expressions. (shown when Image Mode is url)
Image Thumbnail URLstringNoHTTP/HTTPS URL of the thumbnail image. Maximum 240x240px JPEG. Supports expressions. (shown when Image Mode is url)
Binary PropertystringNodataName of the binary property containing the image file to upload. Names are case-sensitive — see the upstream node’s Binary Data panel for the exact names to use. (shown when Image Mode is binary)
Sticker Package IDnumberNoLINE sticker package ID. Must be provided together with Sticker ID. See LINE sticker list for valid values. Supports expressions.
Sticker IDnumberNoLINE sticker ID. Must be provided together with Sticker Package ID. Supports expressions.
Notification DisabledbooleanNofalseWhen true, the recipient does not receive a push notification (the message still appears in the LINE conversation).
Max ConcurrencynumberNo10Maximum number of items to process concurrently.

Output Data

One output item per input item. The LINE Notify API response is merged into the item JSON — the rest of the incoming fields pass through and binary data is forwarded unchanged.

Two fields are written onto the item:

{
  "status": 200,
  "message": "ok"
}
  • status — the status code LINE Notify returned for the notification.
  • message — LINE Notify’s result text. This overwrites an incoming message field of the same name, so rename it upstream if you need to keep it.

Reference the result downstream by expression, e.g. {{ $json.status }}.

Usage Examples

  • Send a text notification to a LINE group
  • Send an image notification with a binary file upload
  • Send a notification with a LINE sticker
  • Send a silent notification (no push) to LINE

Example Configuration

Send a plain text notification:

{
  "type": "line",
  "parameters": {
    "message": "Deployment finished for {{ $json.service }}"
  }
}

Attach an image by URL:

{
  "type": "line",
  "parameters": {
    "message": "Check out this image!",
    "imageMode": "url",
    "imageFullsize": "https://example.com/images/fullsize.jpg",
    "imageThumbnail": "https://example.com/images/thumbnail.jpg"
  }
}

Upload an image from an upstream node’s binary data:

{
  "type": "line",
  "parameters": {
    "message": "Screenshot attached",
    "imageMode": "binary",
    "binaryPropertyName": "screenshot"
  }
}

Add a sticker to the notification:

{
  "type": "line",
  "parameters": {
    "message": "Monthly target achieved",
    "stickerPackageId": 446,
    "stickerId": 1988
  }
}

Send a silent, high-throughput batch:

{
  "type": "line",
  "parameters": {
    "message": "System maintenance completed successfully",
    "notificationDisabled": true,
    "maxConcurrency": 20
  }
}

Error Handling

ModeBehavior
stopHalts workflow on first error
continueSkips failed items, passes successful ones through
errorPortRoutes failed items to Error output port

Tips

Send LINE Notify notifications with optional image (URL or binary upload) and sticker attachments.

  • You do not choose the recipient here. The notification goes wherever the access token was bound at authorization time — one token per user or group. To notify several destinations, create one credential per destination.
  • Image Mode is exclusive. url uses Image Full Size URL and Image Thumbnail URL; binary uploads the file named by Binary Property. Only the fields belonging to the selected mode are sent.
  • Stickers are all-or-nothing. Sticker Package ID and Sticker ID must both be set, or neither is sent.
  • Notification Disabled still delivers the message — it only suppresses the recipient’s push alert, so the text still appears in the LINE conversation.

Frequently asked questions

How do I choose who receives the notification?

You do not choose it here. The notification goes wherever the access token was bound at authorization time — one token per user or group. To notify several destinations, create one credential per destination.

How do I attach an image?

Image Mode is exclusive: `url` uses the Image Full Size URL and Image Thumbnail URL fields, while `binary` uploads the file named by Binary Property. Only the fields belonging to the selected mode are sent.

How do stickers work?

They are all-or-nothing — the sticker identifiers must be supplied together for the sticker to attach, rather than partially filled in.

Which credential does it need?

A LINE Notify credential holding the access token, which also determines the destination.

Build with the Line node

Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need LINE Notify credentials first.

Open BusyBot

Last updated . Spotted something wrong? Tell us.