← All N8N workflows
Automation & utilitiesExtract From FileHTTP RequestSwitchWebhook

Chinese Translator

Configured with Extract From File, HTTP Request, Switch, Webhook. Review the connections and setup before adapting this template.

Workflow preview
TriggerLine WebhookWebhookWeb / APILine Loading AnimationHTTP RequestRoutingSwitchSwitchWeb / APIGet ImageHTTP RequestWeb / APIOpenRouter :qwen/qwen2.5-vl-72b-in…HTTP RequestWeb / APIOpenRouter:qwen/qwen-2.5-72b-inst…HTTP RequestTransformExtract from FileExtract From FileWeb / APILine Reply (image)HTTP RequestWeb / APILine Reply (Text)HTTP RequestWeb / APILine Reply (NotSupported 2)HTTP RequestWeb / APILine Reply (NotSupported 1)HTTP Request

Node categories in this workflow

  • Trigger
  • Web / API
  • 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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Line WebhookTriggerWebhookSee node parameters
Line Loading AnimationWeb / APIHTTP RequestPOST
SwitchRoutingSwitchSee node parameters
Get ImageWeb / APIHTTP RequestSee node parameters
OpenRouter : qwen/qwen2.5-vl-72b-instruct:freeWeb / APIHTTP RequestPOST
OpenRouter: qwen/qwen-2.5-72b-instruct:freeWeb / APIHTTP RequestPOST
Extract from FileTransformExtract From FilebinaryToPropery
Line Reply (image)Web / APIHTTP RequestPOST
Line Reply (Text)Web / APIHTTP RequestPOST
Line Reply (Not Supported 2)Web / APIHTTP RequestPOST
Line Reply (Not Supported 1)Web / APIHTTP RequestPOST

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

Sticky Note1

Webhook from Line

You need to set-up this webhook at Line Manager or Line Developer Console

You'll need to copy Webhook URL from this node to put in Line Console

Also, don't forget to remove 'test' part when going for production

https://developers.line.biz/en/docs/messaging-api/receiving-messages/

Sticky Note2

Line Loading Animation

This node is to only give ... loading animation back in Line.

It seems stupid but it actually tells user that the workflow is running and you are not left waiting without hope

To authorize, you can fill in the Line Token in the node here, or you can you header authorization (shown at the 'reply message' node)

https://developers.line.biz/en/docs/messaging-api/use-loading-indicator/

Sticky Note

OpenRouter.ai

This is to call LLMs model at Openrouter.ai

You can use it to call ChatGPT, Lllama, Qwen, Deepseek, and much more with just standardized API call and top-up only once

https://openrouter.ai/docs/quickstart

Sticky Note3

Line Reply

This node is to send reply message via Line

https://developers.line.biz/en/docs/messaging-api/sending-messages/

Sticky Note5

**Router for Text, Image, Voice, and others

Sticky Note6

Line Reply Similar to above but from different route

Sticky Note7

OpenRouter.ai We will use image as prompt and change the model to support image.

Sticky Note8

Pre-processing

We need to use get media API to get the data from Line and also move it to base64 file to prompt

Sticky Note9

Line Reply To reply that message is not supported

Chinese Translator

Chinese Translator

Purpose and structure

This folder contains the Chinese Translator workflow. Its executable nodes use extractFromFile, httpRequest, switch, 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

Line Webhook

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/1885_HTTP_Extractfromfile_Automation_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • You can test this workflow by adding Line @405jtfqs

More in Automation & utilities