HumationHuman + Automation
Back to Catalog

Monitor NASA asteroid threats with AI fact-check and multi-channel alerts

AsukaAsuka
72 views
2/3/2026
Google SheetsUser ManagementAutomationUpvotyHTTP Request
Official Page

Who Is This For?

This workflow is designed for space enthusiasts, science educators, journalists, fact-checkers, and researchers who want to stay informed about near-Earth asteroid threats while filtering out media sensationalism. It's also valuable for anyone studying how different regions cover space-related news.

What It Does

This workflow creates an automated planetary defense monitoring system that:

  • Scans NASA's Near Earth Object database for potentially hazardous asteroids over a 7-day window
  • Searches news coverage across three regions (US, Japan, EU) to compare media reporting
  • Uses AI (GPT-4o-mini) to fact-check news claims against official NASA data
  • Detects misinformation and measures media sensationalism levels
  • Generates visual charts comparing actual threat levels vs media panic
  • Sends alerts through multiple channels (Slack, Discord, Email)
  • Logs all alerts to Google Sheets for historical analysis

How It Works

  1. Trigger: Runs daily at 9 AM or on-demand via webhook
  2. NASA Data Fetch: Retrieves 7-day asteroid forecast from NASA NeoWs API
  3. Threat Analysis: Identifies potentially hazardous asteroids and assigns alert levels (LOW/MEDIUM/HIGH)
  4. News Search: Searches news in US, Japan, and EU using Apify's Google Search Scraper
  5. AI Fact-Check: GPT-4o-mini compares news claims against NASA data, detecting misinformation
  6. Visualization: Generates gauge charts for threat level and media panic, plus regional comparison bar chart
  7. Multi-Channel Alerts: Sends formatted reports to Slack, Discord, Email, and logs to Google Sheets

Set Up Steps

Estimated time: 15-20 minutes

  1. NASA API (Required): Get your free API key at api.nasa.gov
  2. Apify (Required): Create account and connect via OAuth
  3. OpenAI (Required): Add your API key from platform.openai.com
  4. Notification Channels (Choose at least one):
    • Slack: Create OAuth app and connect
    • Discord: Create webhook URL
    • Email: Configure SMTP settings
  5. Google Sheets (Optional): Create a sheet for logging with columns: Date, Alert Level, Hazardous Count, Threat Score, Media Panic Score, Misinformation Detected, Top Asteroid, Most Accurate Region

Requirements

  • NASA API key (free)
  • Apify account (free tier available)
  • OpenAI API key (paid)
  • At least one notification channel configured
  • n8n version 1.0+

How to Customize

  • Change scan frequency: Modify the Schedule Trigger node
  • Add more regions: Edit the "Configure Regional Search" code node
  • Adjust alert thresholds: Modify lunar distance threshold (currently 10) in "Analyze Asteroid Threats"
  • Disable channels: Simply remove connections to notification nodes you don't need
  • Customize messages: Edit the "Format Multi-Channel Messages" node

n8n Workflow: Monitor NASA Asteroid Threats with AI Fact-Check and Multi-Channel Alerts

This n8n workflow automates the process of monitoring NASA's Near-Earth Objects (NEO) data, applying AI-powered fact-checking, and delivering multi-channel alerts for potentially hazardous asteroids. It helps you stay informed about asteroid threats by providing a robust, automated notification system.

What it does

This workflow performs the following key steps:

  1. Scheduled Data Fetch: Periodically fetches the latest Near-Earth Object (NEO) data from the NASA API.
  2. AI Fact-Checking: For each asteroid identified, it uses OpenAI to generate a "fact-check" or summary, potentially assessing its threat level or other relevant information.
  3. Threat Assessment: Filters the asteroids based on a defined condition (e.g., "is_potentially_hazardous_asteroid").
  4. Multi-Channel Alerts:
    • If an asteroid is deemed potentially hazardous, it sends a detailed alert via Slack, Discord, and Email.
    • It also logs all asteroid data (both hazardous and non-hazardous) to a Google Sheet for historical tracking and analysis.
  5. Webhook Response: Provides a response to the initial webhook trigger, if applicable (though this workflow is primarily schedule-triggered, the webhook response node is present).

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • NASA API Key: An API key for NASA's Open API (specifically for the Near-Earth Object Web Service).
  • OpenAI API Key: An API key for OpenAI to utilize its language model for fact-checking.
  • Slack Account: A Slack workspace and a configured Slack credential in n8n to send messages.
  • Discord Account: A Discord server and a configured Discord credential in n8n to send messages.
  • SMTP Credentials: SMTP server details and credentials to send email notifications.
  • Google Sheets Account: A Google account with access to Google Sheets, and a configured Google Sheets credential in n8n. You will need to create a Google Sheet to store the asteroid data.

Setup/Usage

  1. Import the Workflow:
    • Download the workflow JSON provided.
    • In your n8n instance, click "New" in the workflows list, then "Import from JSON" and paste the workflow JSON.
  2. Configure Credentials:
    • For each node requiring credentials (NASA, OpenAI, Slack, Discord, Send Email, Google Sheets), click on the node and select or create the appropriate credential.
    • Ensure your NASA API key is correctly configured in the NASA node.
    • Ensure your OpenAI API key is correctly configured in the OpenAI node.
    • Set up your Slack, Discord, and SMTP credentials.
    • Configure your Google Sheets credential and specify the Spreadsheet ID and Sheet Name where you want to log the data.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule (e.g., daily, hourly) in the "Schedule Trigger" node according to your monitoring frequency needs.
    • NASA Node: Ensure the "Operation" is set to retrieve NEO data.
    • OpenAI Node: Customize the prompt in the OpenAI node to refine the fact-checking or summary generation for asteroids.
    • If Node: Review and adjust the condition in the "If" node if you want to change what constitutes a "potentially hazardous" asteroid (e.g., based on specific orbital parameters, size, etc.).
    • Slack, Discord, Send Email Nodes: Customize the message templates to include the specific asteroid data you want to highlight in your alerts.
    • Google Sheets Node: Ensure the column names in the Google Sheet match the data you are sending from the workflow.
  4. Activate the Workflow: Once all configurations are complete, activate the workflow. It will start running automatically based on your defined schedule.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942