Email summaries from OpenRouter sent to a LINE chat

Email summaries from OpenRouter sent to a LINE chat

An n8n workflow that reads new mail over IMAP, sends each message to a model on OpenRouter for a short summary, and pushes the summary to a LINE chat through LINE's Messaging API.

What is inside

• workflow.json: the workflow as n8n exports it, seven nodes: three that do the work and four sticky notes. It holds no credential.
• README.md: these notes.

What we changed from the original copy

• The credential links are gone. Select your own for IMAP and for the two Header Auth steps.
• The model was meta-llama/llama-3.1-70b-instruct:free. OpenRouter's public model list, read on 12 November 2026, no longer shows it. The same model without :free is listed with a context of 131072 tokens and a price of 0.00000072 USD per token for input and output, and the node uses it. It is no longer free.
• Read emails (IMAP) moves from version 2 to 2.2. In n8n's source, versions up to 2 do not remember the last message seen, and this file leaves mail unread after processing. Each new arrival would then fetch every unread message again. Version 2.2 follows the message ids.
• The email text in the prompt was URL-encoded, which keeps quotes and line breaks from breaking the JSON body but gives the model percent-encoded text. It is JSON-escaped now, and the plain text part is used, with the HTML part as a fallback. The summary sent to LINE is escaped the same way, so a quote in it cannot break the request.
• The LINE user id is <YOUR_LINE_USER_ID> now.
• The notes are rewritten. Two links and a remark about LINE's own node are removed.
• Nothing else.

Before you start

• An n8n instance, on n8n Cloud or your own server.
• A mailbox you can reach over IMAP, with its host, port and login.
• An OpenRouter account and an API key.
• A LINE channel with the Messaging API, its channel access token, and the user id of the person who should get the summaries.

Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick workflow.json.
2. Add an Email (IMAP) credential and select it in Read emails (IMAP).
3. Add a Header Auth credential for OpenRouter. Set the name to Authorization and the value to Bearer <YOUR_OPENROUTER_API_KEY>, with your key in place of the placeholder. Select it in Send email to A.I. to summarize.
4. Add a second Header Auth credential for LINE with the name Authorization and the value Bearer <YOUR_LINE_CHANNEL_ACCESS_TOKEN>. Select it in Send summarized content to messenger.
5. In that node, replace <YOUR_LINE_USER_ID> with the receiver's user id.
6. Save and activate the workflow, then send yourself a mail.

How a run goes

1. Read emails (IMAP) reads the inbox and fires for unread mail. It leaves each message unread.
2. Send email to A.I. to summarize posts the sender, subject and text to OpenRouter's chat completions address. The prompt asks for a summary of under ten words when the mail is unimportant, and for deadlines and action items, with an urgent marker, when it matters.
3. Send summarized content to messenger posts the summary as a text message to LINE's push address.

Change the look

• The instructions to the model: the prompt in Send email to A.I. to summarize.
• The model: model in the same body.
• Which mail is read: the mailbox and options in Read emails (IMAP).
• Who receives the summary: to in the LINE body.

Good to know

• LINE's pricing page, read on 12 November 2026, counts push messages toward a plan's message count. Reply messages are not counted.
• OpenRouter bills the model per token.
• An email with only an HTML part sends that HTML to the model, which makes a long prompt.
• This copy was not run against a mail server, OpenRouter or LINE.
• The sender, subject and body go to OpenRouter and its model provider. The summary goes to LINE.
• The JSON holds no credential.