line message api demo
Configured with HTTP Request, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Trigger
- Routing
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Line : Reply with token | Web / API | HTTP Request | POST |
| Webhook from Line Message | Trigger | Webhook | See node parameters |
| If | Routing | If | See node parameters |
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Line : Push Message | Web / API | HTTP Request | POST |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuth
Workflow notes
Line Message API Reply
Line Message API Reply
Received Message from user and reply with same text by using reply token
There are many event types. So we need to determine if the type is message.
Line Message API Send Message
Line Message API Send Message
You need to get the Line UID first. Every user is differnt.
If you have the Line UID. Then you can push the message to the User.
line message api demo
line message api demo
Purpose and structure
This folder contains the line message api demo workflow. Its executable nodes use httpRequest, if, manualTrigger, set, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Webhook from Line Message, When clicking ‘Test workflow’
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/1799_HTTP_Manual_Send_Webhook.json MIT; preserve source notices.