LINE Messaging API in n8n: Reply Token & Push Message Workflow

Reply and push messages on LINE—directly from n8n

This n8n workflow shows you how to integrate the LINE Messaging API to handle two real messaging scenarios: replying to a user’s message using a reply token and sending a push message using a user ID. Get a working blueprint for LINE bot communication with clean, conditional routing.

What this workflow does

• Receives incoming LINE events via a webhook in n8n (HTTP POST to your {n8n-webhook-page} endpoint).
• Checks the event type using an If condition: it verifies whether {{ $json.body.events[0].type }} equals "message".
• Replies automatically with a reply token by calling the LINE Messaging API endpoint for replies (HTTP POST to https://api.line.me/v2/bot/message/r).
• Sends a push message to a specific user (test workflow step) using the recipient’s unique user ID.

Use cases

• Customer support bot: reply instantly when a LINE user messages your account.
• Announcement/testing workflow: push a message to a known LINE user ID for QA or internal updates.
• Operator-driven outreach: use n8n to trigger LINE messages from other systems while still supporting reply-token responses.

Technical details

• Webhook integration: captures LINE incoming events with an n8n webhook (POST to {n8n-webhook-page}).
• Conditional logic: If node filters events where type is "message".
• HTTP Request actions: performs the LINE API calls for both reply (reply token) and push (user ID).
• Pre-configuration (credential): create a Header Auth credential named Authorization with value Bearer {line token} to authenticate LINE API requests.
• Nodes used: if, set, webhook, sticky note, http request, manual trigger.