OpenRuna
Sign in
← Workflows

1841_Telegram_Manual_Automate_Triggered

17 nodes · gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram

Engine
n8n
Nodes
17
Trigger
scheduled/triggered
Source file
1841_Telegram_Manual_Automate_Triggered.json

Workflow flow

IntegrationsGmailManualLmChatGoogleGeminiAgentOutputParserStructuredTelegramAggregate@n8n/n8n-nodes-langchain.lmChatGoogleGemini@n8n/n8n-nodes-langchain.agent@n8n/n8n-nodes-langchain.outputParserStructuredIFNoOp+1 more
100%
TRIGGER

When clicking ‘Test workflow’

Manual

Google Gemini Chat Model

@n8n/n8n-nodes-langchain.lmChatGoogleGemini

Unwanted Email Output Parser

@n8n/n8n-nodes-langchain.outputParserStructured

Initialize Loop Vars

Set

Increment Loop Var

Set

Gmail Get Email

Gmail

AI Check Email

@n8n/n8n-nodes-langchain.agent

If Unwanted Marketing or Spam

IF

Telegram Sent Email Deleted Notification

Telegram

Telegram Sent Email Not Deleted Notification

Telegram

Telegram Sent AI Error Notification

Telegram

Telegram Sent Delete Email Failed Notification

Telegram

Aggregate

Aggregate

GmailDeleteEmail

Gmail

Success

NoOp

Forward Prev Page Num

Set

Gmail

Gmail

17 steps · flows top to bottom, branches left to right

Browse by integration

gmailmanuallmChatGoogleGeminiagentoutputParserStructuredtelegramaggregate
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: 1841_Telegram_Manual_Automate_Triggered. 17 nodes across gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "1841_Telegram_Manual_Automate_Triggered", wires together gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate in 17 nodes. 17 nodes · gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "1841_Telegram_Manual_Automate_Triggered" into n8n, reconnect credentials for gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate, and run the same automation in your own workspace.
  • Use it as a starting template when wiring gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate — adjust node parameters to your accounts and record IDs.
  • Study how data moves from gmail to manual before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the gmail stack.

Example output

Imported into n8n, "1841_Telegram_Manual_Automate_Triggered" exposes 17 configured nodes. Trigger type: scheduled/triggered. Integrations: gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate. Open each node after import to map credentials to your own gmail and manual accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "1841_Telegram_Manual_Automate_Triggered" JSON into a plain-English runbook, node by node. It can flag where gmail rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "1841_Telegram_Manual_Automate_Triggered" — extract gmail IDs and secrets into environment variables without changing the 17-node structure.

Frequently asked questions

How do I import "1841_Telegram_Manual_Automate_Triggered" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "1841_Telegram_Manual_Automate_Triggered" use?
It uses: gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate. The flow diagram above shows how each service connects across the 17 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own gmail and manual credentials in n8n after import.
What trigger type does "1841_Telegram_Manual_Automate_Triggered" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "1841_Telegram_Manual_Automate_Triggered" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for gmail, manual, lmChatGoogleGemini, agent, outputParserStructured, telegram, aggregate.

Related resources