Automated asteroid alerts with NASA API, Slack & Google Calendar
This n8n template creates an automated alert system that checks NASA's data for near-Earth asteroids twice a day. When it finds asteroids meeting specific criteria, it sends a summary alert to Slack and creates individual events in Google Calendar for each object.
Use cases
- Automated Monitoring: Keep track of potentially hazardous asteroids without manually checking websites.
- Team or Community Alerts: Automatically inform a team, a group of friends, or a community about significant celestial events via Slack.
- Personalized Space Calendar: Populate your Google Calendar with upcoming asteroid close approaches, creating a personal "what's up in space" agenda.
- Educational Tool: Use this as a foundation to learn about API data fetching, data processing, and multi-channel notifications in n8n.
Good to know
- This workflow runs on a schedule (every 12 hours by default) and does not require a manual trigger.
- NASA API Key is highly recommended. The default
DEMO_KEYhas strict rate limits. Get a free key from api.nasa.gov. - The filtering logic for what constitutes an "alert-worthy" asteroid (distance and size) is fully customizable within the "Filter and Process Asteroids" Code node.
How it works
- A Schedule Trigger starts the workflow every 12 hours.
- The "Calculate Date Range" Code node generates the start and end dates for the API query (today to 14 days from now).
- The NASA node uses these dates to query the Near Earth Object Web Service (NeoWs) API, retrieving a list of all asteroids that will pass by Earth in that period.
- The "Filter and Process Asteroids" Code node iterates through the list. It filters out objects that are too small or too far away, based on thresholds defined in the code. It then formats and sorts the remaining "interesting" asteroids by their closest approach distance.
- An If node checks if any asteroids were found after filtering.
- If true (asteroids were found), the flow continues to the alert steps.
- If false, the workflow ends quietly via a NoOp node.
- The "Format Alert Messages" Code node compiles a single, well-formatted summary message for Slack and prepares the data for other notifications.
- The workflow then splits into two parallel branches:
- Slack Alert: The Slack node sends the summary message to a specified channel.
- Calendar Events: The Split Out node separates the data so that each asteroid is processed individually. For each asteroid, the Google Calendar node creates an all-day event on its close-approach date.
How to use
-
Configure the NASA Node:
- Open the "Get an asteroid neo feed" (NASA) node.
- Create new credentials and replace the default
DEMO_KEYwith your own NASA API key.
-
Customize Filtering (Optional):
- Open the "Filter and Process Asteroids" Code node.
- Adjust the
MAX_DISTANCE_KMandMIN_DIAMETER_METERSvariables to make the alerts more or less sensitive.// Example: For closer, larger objects const MAX_DISTANCE_KM = 7500000; // 7.5 million km (approx. 19.5 lunar distances) const MIN_DIAMETER_METERS = 100; // 100 meters
-
Configure Slack Alerts:
- Open the "Send Slack Alert" node.
- Add your Slack OAuth2 credentials.
- Select the channel where you want to receive alerts (e.g.,
#asteroid-watch).
-
Configure Google Calendar Events:
- Open the "Create an event" (Google Calendar) node.
- Add your Google Calendar OAuth2 credentials.
- Select the calendar where events should be created.
-
Activate the workflow.
Requirements
- A free NASA API Key.
- Slack credentials (OAuth2) and a workspace to post alerts.
- Google Calendar credentials (OAuth2) to create events.
Customising this workflow
- Add More Notification Channels: Add nodes for Discord, Telegram, or email to send alerts to other platforms.
- Create a Dashboard: Instead of just sending alerts, use the processed data to populate a database (like Baserow or Postgres) to power a simple dashboard.
- Different Data Source: Modify the HTTP Request node to pull data from other space-related APIs, like a feed of upcoming rocket launches.
Automated Asteroid Alerts with NASA API, Slack & Google Calendar
This n8n workflow automates the process of fetching information about potentially hazardous asteroids from the NASA API, filtering them based on specific criteria, and then notifying a Slack channel and creating a Google Calendar event for each relevant asteroid.
What it does
This workflow streamlines asteroid monitoring and alerting by performing the following steps:
- Triggers on Schedule: The workflow runs on a predefined schedule (e.g., daily) to fetch the latest asteroid data.
- Fetches Asteroid Data: It queries the NASA API for Near-Earth Objects (NEOs).
- Processes Asteroid Data: It extracts relevant information about each asteroid, such as its name, estimated diameter, close approach date, and whether it's potentially hazardous.
- Filters Potentially Hazardous Asteroids: It uses a conditional logic to identify only those asteroids classified as "potentially hazardous."
- Notifies Slack: For each potentially hazardous asteroid, it posts a detailed alert message to a specified Slack channel.
- Creates Google Calendar Event: It creates a Google Calendar event for each potentially hazardous asteroid, marking its close approach date and time.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- NASA API Key: An API key from NASA to access their Near-Earth Object Web Service (NeoWs).
- Slack Account: A Slack workspace and a channel where alerts should be posted.
- Google Calendar Account: A Google account with access to Google Calendar where events will be created.
Setup/Usage
- Import the Workflow:
- Download the provided JSON file.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON or upload the file.
- Configure Credentials:
- NASA: Add your NASA API key as a credential in n8n.
- Slack: Set up a Slack credential in n8n, granting it the necessary permissions to post messages to your chosen channel.
- Google Calendar: Configure a Google Calendar credential (OAuth2 recommended) with permissions to create events.
- Customize Workflow Nodes:
- Schedule Trigger (Node 839): Adjust the schedule to your preferred frequency (e.g., once a day, every few hours).
- NASA (Node 421): Ensure your NASA API key credential is selected.
- Code (Node 834): This node likely processes the raw NASA API response. Review its JavaScript code to understand how data is extracted and transformed. You might need to adjust it if the NASA API response structure changes or if you need different data points.
- If (Node 20): This node filters for "potentially hazardous" asteroids. Review its conditions to ensure they match your desired filtering logic.
- Slack (Node 40): Select your Slack credential and specify the channel where alerts should be posted. Customize the message content as needed using expressions to include asteroid data.
- Google Calendar (Node 317): Select your Google Calendar credential and specify the calendar to use. Configure the event details (title, description, start/end times) using expressions from the asteroid data.
- Activate the Workflow: Once all credentials are set and nodes are configured, activate the workflow. It will start running according to the schedule you defined.
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.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte