Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This workflow automates the process of notifying users about new emails via Telegram and temporarily hosting the email content on a secret HTML page. It is ideal for users who need immediate notifi...

Best for

Personal Productivity automation workflows
intermediate n8n builders looking for reusable templates

Tools used

n8n-nodes-base.emailreadimap, n8n-nodes-base.telegram, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Nskha.

Original n8n.io source

1.1 Workflow description

Title: Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist
Workflow name: Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist

Overview

Use Cases

Immediate notification of new emails in Telegram with the ability to preview the email content in a secure, temporary HTML format.
Automation for users who need to keep track of their emails without constantly checking their email client.
Useful for teams or individuals who require instant updates on critical emails and prefer a quick preview through a web interface.

My Personal Use Case: Secure Subscription Sharing

From time to time, I find myself wanting to share my paid subscriptions with friends, but giving out OTP codes manually or sharing my email isn't a good idea due to security concerns. I attempted to use the IMAP node to integrate with Telegram secret channel for this purpose but encountered numerous problems, such as difficulties in scraping content from emails. Additionally, the Telegram API sometimes rejects certain special characters found within email contents. After facing these challenges, I discovered that rendering emails as HTML pages and sharing them directly is the most effective solution. This approach bypasses the issues with character limitations and content scraping, providing a seamless way to share subscription benefits securely.

Services/APIs Used

Service/API	Node Type	Description
IMAP Email Server	Email Trigger (IMAP)	Triggers the workflow on receiving a new email.
Telegram API	Telegram	Sends notifications and manages messages in Telegram.
GitHub Gist API	HTTP Request (Github Gist)	Temporarily hosts email content on GitHub Gist.
GitHub Gist API (Deletion)	HTTP Request (Github Gist ‌)	Deletes the temporary GitHub Gist after a specified time.
Wait	Wait	Delays the workflow for a specified period.

Configuration Steps

Email Trigger (IMAP): Configure your IMAP email credentials to enable the workflow to check for new emails.
Telegram Nodes: Insert your Telegram bot's API credentials and your chat ID in both Telegram nodes to send and delete messages.
Github Gist Nodes: Provide your GitHub API credentials to create and delete Gists. Ensure the GitHub token has the necessary permissions to create and delete Gists.
Wait Node: Adjust the wait time according to your preference for how long the email content should be accessible via the HTML page.

Screenshot

Additional Notes

Ensure all credentials are securely stored and have the minimum necessary permissions for the workflow to function.
Test the workflow with non-sensitive emails to ensure it operates as expected before using it with critical email accounts.
Consider the privacy and security implications of temporarily hosting email content on GitHub Gist.

For any questions or issues, refer to the respective API documentation for each service used or consult the n8n community for support.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Email Trigger (IMAP)

Type / Role: n8n-nodes-base.emailReadImap - emailReadImap
Config choices: Version 2

Block 2 - Telegram

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.1

Block 3 - Github Gist

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

Block 4 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 5 - Wait

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1

Block 6 - Telegram ‌

Type / Role: n8n-nodes-base.telegram - telegram
Config choices: Version 1.1

Block 7 - Github Gist ‌

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.1

3. Summary Table

Workflow	Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist
Complexity	intermediate
Nodes	7
Categories	Personal Productivity
Author	Nskha
Published	03 Feb 2024

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/2080/2080.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Personal Productivity workflows

Frequently asked questions

What does Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Personal Productivity use case.

Nskha

9 workflows

Nodes

n8n-nodes-base.emailreadimap n8n-nodes-base.telegram n8n-nodes-base.httprequest n8n-nodes-base.stickynote n8n-nodes-base.wait

Complexity

intermediate

Published 03 Feb 2024

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/2080/2080.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Manage Google Calendar events with Zalo Bot, OpenAI and Gemini

## Quick Overview This workflow lets users manage Google Calendar by sending text or voice messages to a Zalo Official Account bot, transcribing voice notes with Google Gemini and using an OpenAI-powered agent to create, update, list, or delete events, then replying in Zalo with the result. ## How it works 1. Receives an incoming text or voice message through a Zalo Bot trigger. 2. Sends a typing indicator back to the Zalo chat and normalizes key message fields (chat ID, type, text, and voice URL). 3. If the message is a voice note, sends the audio URL to Google Gemini to transcribe it into text. 4. Sends the combined text/transcription to an OpenAI chat model agent that interprets the request in Vietnamese and decides whether to list, create, update, or delete a Google Calendar event. 5. Uses Google Calendar tools to get events and then create, update, or delete the targeted event based on the agent’s extracted parameters. 6. Sends the agent’s Markdown-formatted response back to the user in Zalo, and posts an error message to Zalo if the agent run fails. ## Setup 1. Install the community node package `n8n-nodes-zalo-bot-official` and restart n8n if required. 2. Connect your Zalo Bot API credentials and configure the Zalo webhook URL in your Zalo Official Account so incoming messages reach this workflow. 3. Add a Google Calendar OAuth2 credential and set the target calendar account (currently configured as `[email protected]`) for all calendar operations. 4. Add a Google Gemini (PaLM) API credential for audio transcription and ensure voice messages include a reachable `voice_url`. 5. Add an OpenAI API credential, select the chat model you want to use (currently `gpt-5-mini`), and adjust the system prompt/tone if needed.

View

Screen LinkedIn jobs and generate tailored resume and cover PDFs with Anthropic and DocRaptor

## Quick Overview This workflow collects your job preferences and resume via an n8n form, scrapes fresh LinkedIn job listings with Apify, screens and ranks matches using Anthropic Claude, generates tailored resume and cover letter PDFs via DocRaptor, then emails them to you and logs each match in Google Sheets. ## How it works 1. Receives a form submission with your email, target role, seniority, locations, skills, deal-breakers, and resume text. 2. Calls the Apify LinkedIn Job Scraper API to fetch up to 150 jobs posted in the last 7 days for the provided keywords and location. 3. Removes duplicates and filters out obvious mismatches based on seniority, required years of experience patterns, and location rules. 4. Uses Anthropic Claude (Haiku) to score each remaining job for relevance and eligibility and returns a JSON verdict and fit score. 5. Ranks the results, drops rejected roles, and keeps the top five best-scoring matches. 6. Uses Anthropic Claude (Sonnet) to generate a structured resume JSON and cover letter JSON tailored to each shortlisted job using only facts from your provided profile. 7. Renders the resume and cover letter to HTML, converts them to PDF files with DocRaptor, emails the PDFs to you via Gmail, and appends a tracker row to Google Sheets. ## Setup 1. Add credentials for Anthropic (Claude), Gmail, Google Sheets, and DocRaptor (HTTP Basic Auth with your API key as the username and a blank password). 2. Replace YOUR_APIFY_TOKEN in the Apify HTTP request URL and ensure you have access to the Apify LinkedIn Jobs Scraper actor endpoint used in the workflow. 3. Create a Google Sheet with a “Tracker” tab and set the document ID (YOUR_TRACKER_SHEET_ID) to match your sheet. 4. If you want non-watermarked PDFs, set DocRaptor "test" to false in both PDF generation requests.

View

Triage and route tasks with Google Sheets, GPT-4o-mini, Gmail, Slack, and Google Tasks

## Quick Overview This workflow collects tasks via a webhook, stores validated tasks in Google Sheets, and runs a daily prioritization routine that creates urgent items in Google Tasks with Slack alerts while summarizing medium/low tasks with OpenAI and emailing the digest via Gmail. ## How it works 1. Receives a POST webhook request containing task details and normalizes fields like priority and due date. 2. Validates required fields (including allowed priority values) and rejects invalid submissions with an error. 3. Appends valid tasks to Google Sheets with a pending status and returns a success response to the webhook caller. 4. Runs daily on a schedule, reads tasks from Google Sheets, keeps only pending items, removes duplicates, and sorts them by priority. 5. For high-priority tasks, creates a Google Tasks item and sends a Slack alert. 6. For medium and low-priority tasks, compiles a digest, generates an email-ready summary with OpenAI, and sends it via Gmail. 7. Updates each handled task in Google Sheets with a Processed status and a processed timestamp. ## Setup 1. Create a Google Sheet with columns for taskName, priority, category, dueDate, status, createdAt, and processedAt, and update the spreadsheet and sheet IDs in the Google Sheets steps. 2. Add Google Sheets OAuth2 credentials for both reading and updating/appending rows. 3. Add credentials for Google Tasks, Slack (OAuth2), Gmail, and OpenAI, and set the target Google Task list, Slack destination, and email recipients/subject as needed. 4. Copy the webhook URL from the webhook trigger and configure your task intake source to send POST requests with fields like "Task Name", "Priority", "Category", and "Due Date". 5. Adjust the schedule time and any validation rules (required fields and accepted priority values) to match your process.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Email notifications to Telegram using temporary HTML URL hosting via GitHub Gist

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Overview

Use Cases

My Personal Use Case: Secure Subscription Sharing

Services/APIs Used

Configuration Steps

Screenshot

Additional Notes

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Email Trigger (IMAP)

Block 2 - Telegram

Block 3 - Github Gist

Block 4 - Sticky Note

Block 5 - Wait

Block 6 - Telegram ‌

Block 7 - Github Gist ‌

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions