Resources · n8n integration

Line n8n integrationAutomate Line with n8n.

One node, one job: push a message into a Line chat from any workflow. The Line n8n integration comes down to a single operation, Send a notification, a Notify OAuth2 connection and 3 optional fields. Read the setup steps and the deprecation note before you build on it.

Try the Line integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What can the Line n8n integration actually do?

The Line n8n integration is the built-in Line node, filed under Communication and shipped with n8n itself. It holds one resource, Notification, and one operation that sends a message to the users or groups attached to a Line Notify service. Nothing to install: you set up a credential once, meaning the stored connection n8n keeps for you, and the node offers it in a dropdown inside every workflow you build afterwards.

Workflows that end in Line tend to look alike at the tail and differ at the head. The daily briefing is the most common shape, and a public template already does it: OpenWeatherMap pulls the forecast, the Line node drops it in the group chat before anyone opens a laptop (workflow 773).

Alerting is the second shape. Another public template watches NASA data for asteroid passes, runs the text through OpenAI and DeepL, then posts the result to Line (workflow 11304). The pattern generalizes: whatever produces the signal, the last node is the same one, with the message assembled just before it.

The third shape is internal reporting. A Schedule Trigger, which is simply a node that starts a workflow on a clock, reads a tracking sheet through Google Sheets, counts what needs attention and sends one line to the team chat. Same idea as a message to Slack or Telegram, only the destination changes.

Because the node carries a single operation, anything else on the Line side has no matching node field. That is where HTTP Request comes in: it calls any endpoint of the API and can reuse the same stored credential through predefined authentication, so you stay inside one workflow instead of scripting around it.

Now the part that changes the decision. The node is deprecated from n8n 1.64.0, and LINE Notify ended its own service on April 1, 2025, after which the node stops working. So treat this page as documentation of how the node behaves, not as a recommendation to wire a new production alert through it. For a push notification you actually depend on today, Pushover covers the same slot, and the n8n review goes into how the team picks between channels.

Connect

How do you connect Line to n8n?

  1. 01

    Register a service on Line Notify

    You need a Line account, then connect it with Line Notify and add a new service. The form asks for a Service name, which is what people see when they connect to it, a Service description, a Service URL, your Company/Enterprise, a Country/region, a Representative, and a valid Email address. Line verifies that address before the service is fully registered, so pick one you can open right away.

  2. 02

    Match the redirect URL on both sides

    In n8n, start a Line credential with the Notify OAuth2 method. It shows an OAuth Redirect URL: copy it and paste it as the Callback URL in the Line Notify form, agree to the terms and add the service. Open your email, follow the registration link to verify the address, then go back to the services list in Line Notify and select the one you just created.

  3. 03

    Copy the keys and connect the account

    On the service page, copy the Client ID into the n8n credential, choose the option to display the Client Secret and copy that too. Then select the Connect account option in n8n and follow the prompts to finish the handshake. The credential is saved once and reused in every workflow that needs Line, so you never paste these values twice.

Actions

What the Line node does

The Line node exposes 1 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceSend
Notification✓

Notification

1 operation
01

Send a notification

notification.send

What you see in n8n

Notes & use cases

Sends one message to the users or groups linked to the Line Notify service behind the credential, and hands the API response to the next node.

Key parameters

  • Message: the text that lands in the chat, required, often an expression such as {{ $json.summary }} that pulls a value from the item coming in.
  • Notification Disabled: true and the message arrives without a push notification, false and the phone buzzes.
  • Image: an Additional Fields entry (Add Image) that attaches a picture to the message.
  • Sticker: an Additional Fields entry (Add Sticker) for a sticker sent with the text.
Use cases
a nightly job that posts the number of rows flagged for review, sent silently so nobody wakes up for it.
Need help

Need help automating Line with n8n?

A person reads every message.

FAQ

Questions people ask next

01Is the Line n8n integration free?
Yes on the n8n side. The Line node ships with n8n, so there is nothing to install and no add-on to pay for, whether you run n8n Cloud or self-host with Docker or npm under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places. The Line Notify service sits outside n8n and its own terms are not covered here, so check those separately. One caveat matters more than the price: the node is deprecated from n8n 1.64.0, and free is not the same as working, which the limits question below spells out.
02What credentials does the Line node need?
One method only: Notify OAuth2. You need a Line account plus a Client ID and a Client Secret, and both come from a service you register yourself on Line Notify. The registration form wants a Service name, a Service description, a Service URL, a Company or Enterprise name, a Country or region, a Representative and a valid Email address, which Line verifies by mail before the service counts as registered. The OAuth Redirect URL shown in the n8n credential goes into the Callback URL field of that form. Once saved, the credential is picked from a dropdown in any workflow, so the setup happens once.
03What are the limits of the Line node in n8n?
Two of them, and the second is the one that decides. First, the node exposes a single operation that sends a notification, with Message required and three optional fields around it, so anything else you might want on the Line side has no field in the node. The HTTP Request node covers those calls, reusing the same credential through predefined authentication. Second, the node is deprecated from n8n 1.64.0, and LINE Notify ended its own service on April 1, 2025, after which the node stops working. New alerting work belongs on a channel that is still running.
04Does the Line node react in real time?
There is nothing to react to, because this integration has no trigger node in n8n. A trigger is the node that starts a workflow, and here you supply your own. Three options cover almost everything. A Schedule Trigger runs the workflow on a fixed interval, which fits digests and daily reports. A Webhook, meaning an n8n URL that an outside service calls, starts the workflow the moment that service has something to say. Or another tool's trigger starts it, and Line is only the last node in the chain. The message itself goes out when the workflow reaches that node.
05n8n or Make for this kind of notification?
It depends on four things, and both tools are fine at the job itself. Hosting: n8n runs on your own server with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that, since a self-hosted instance keeps message content on machines you own. Cost model: Make bills per operation, so a workflow that fires often is priced differently than a flat instance you already pay for. Visual logic: both draw the flow on a canvas, and the choice usually comes down to which editor your team reads faster. For Line specifically, the deprecation applies whichever side you pick.
Same platform

Other docs you might need on this stack.

Browse all integrations