Monitor NASA space weather and DSN anomalies with OpenRouter and Telegram

by Ali Abdullah ✓ · 1 views · created 2026-09-23 · Engineering, AI Summarization

What this workflow does

This AI workflow has 12 nodes and runs on a schedule (every minute). Along the way it connects OpenRouter Chat Model, Telegram and Postgres. It also calls eyes.nasa.gov, api.nasa.gov and services.swpc.noaa.gov over HTTP.

How it runs

Trigger: On a schedule (every minute).

1. 🔧 Prepare API Variables (EDIT ME) (Edit Fields (Set)): sets or maps fields
2. 🛰️ Fetch DSN Status XML (HTTP Request): calls eyes.nasa.gov
3. ☀️ Fetch CME Data from NASA (HTTP Request): calls api.nasa.gov
4. 📡 Fetch GOES X-ray Data (HTTP Request): calls services.swpc.noaa.gov
5. ☄️ Fetch NEO Data from NASA (HTTP Request): calls api.nasa.gov
6. Merge: merges the data from its input branches
7. 📊 Process and Aggregate Data (Code): runs custom JavaScript code
8. 🧠 LLM AI Data Analysis (Basic LLM Chain): sends a prompt to an LLM, with model: OpenRouter Chat Model
9. 📲 Send Alert via Telegram (Telegram): uses Telegram
10. 💾 Save Alert to PostgreSQL DB (Postgres): run a query

Services it uses

OpenRouter Chat ModelTelegramPostgres

HTTP calls to: eyes.nasa.gov, api.nasa.gov, services.swpc.noaa.gov

Before you upgrade to n8n 3.0

Nodes used (9)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• Edit Fields (Set)n8n-nodes-base.set
• HTTP Requestn8n-nodes-base.httpRequest
• Mergen8n-nodes-base.merge
• Coden8n-nodes-base.code
• Basic LLM Chain@n8n/n8n-nodes-langchain.chainLlm
• OpenRouter Chat Model@n8n/n8n-nodes-langchain.lmChatOpenRouter
• Telegramn8n-nodes-base.telegram
• Postgresn8n-nodes-base.postgres

From the author

Quick overview This workflow runs every 5 minutes to fetch NASA DSN status, NASA DONKI CME events, NOAA GOES X-ray flux, and NASA NeoWs near‑Earth object data, then uses an OpenRouter-hosted LLM to generate a brief and sends it to Telegram while logging it in…

View the original on n8n.io → Check your own copy