Block 1 - HTTP Request
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
Workflow Execution Video: https://youtu.be/VV4D2aiFXsY Prerequisites & Setup Before you begin, you need to gather a few key pieces of information: 1. N2YO API Key: G...
n8n-nodes-base.httprequest, n8n-nodes-base.telegram, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by iamvaar.
Original n8n.io sourceWorkflow Execution Video: https://youtu.be/VV4D2aiFXsY
Before you begin, you need to gather a few key pieces of information:
https://api.telegram.org/bot<YourBOTToken>/getUpdates. Look for the chat -> id value in the response.This workflow is composed of five nodes that execute in a sequence.
Schedule TriggerHTTP Requesthttps://api.n2yo.com/rest/v1/satellite/visualpasses/25544/...25544 represent the NORAD ID for the International Space Station (ISS).enter-longitude, enter-latitude, and enter-your-api-key with the actual coordinates and API key you gathered during the setup.ReadableHTTP Request node.alert) and calculates the number of minutes until the pass begins (timeinminutes), passing both pieces of information to the next node.Iftimeinminutes value that was calculated in the previous Code node.timeinminutes less than or equal to 600?Send a text messageChat ID is set to the specific chat you want the message to appear in.alert variable created by the Code node. This means it will send the fully formatted message about the upcoming ISS pass.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.
| Workflow | Get real-time international space station visibility alerts with N2YO and Telegram |
|---|---|
| Complexity | intermediate |
| Nodes | 6 |
| Categories | Personal Productivity |
| Author | iamvaar |
| Published | 06 Oct 2025 |
Use the JSON export at /data/workflows/9320/9320.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Workflow Execution Video: https://youtu.be/VV4D2aiFXsY Prerequisites & Setup Before you begin, you need to gather a few key pieces of information: 1. N2YO API Key: G...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.