← All N8N workflows
Messaging & emailEmail Read ImapHTTP RequestTelegramWait

Simple Conversion of Emails into HTML Webpages

Configured with Email Read Imap, HTTP Request, Telegram, Wait. Review the connections and setup before adapting this template.

Workflow preview
MessagingEmail Trigger (IMAP)Email Read ImapMessagingTelegramTelegramWeb / APIGithub GistHTTP RequestWaitWaitWaitMessagingTelegram ‌TelegramWeb / APIGithub Gist ‌HTTP Request

Node categories in this workflow

  • Messaging
  • Web / API
  • Wait

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
Email Trigger (IMAP)MessagingEmail Read ImapSee node parameters
TelegramMessagingTelegramSee node parameters
Github GistWeb / APIHTTP RequestPOST
WaitWaitWaitSee node parameters
Telegram ‌MessagingTelegramdeleteMessage
Github Gist ‌Web / APIHTTP RequestDELETE

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

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

Github Gist

Save HTML content

Simple Conversion of Emails into HTML Webpages

Simple Conversion of Emails into HTML Webpages

To-do:

  • Configure your GitHub credentials through Predefined Credential Type => GitHub API.
  • Add your Telegram credentials by providing your Chat ID.
  • [Optional] You can host this small project on your own domain using GitHub Pages.

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌

Wait

Delete within 3h

Github Gist ‌

Remove HTML content

Simple Conversion of Emails into HTML Webpages

Simple Conversion of Emails into HTML Webpages

Purpose and structure

This folder contains the Simple Conversion of Emails into HTML Webpages workflow. Its executable nodes use emailReadImap, httpRequest, telegram, wait. 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

Inspect connections; no recognized trigger.

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/Telegram/0398_Telegram_Wait_Send_Webhook.json MIT; preserve source notices.

More in Messaging & email