Receive updates of the position of the ISS and add it to a table in TimescaleDB
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 4 nodes and runs on a schedule (legacy Cron node). Along the way it connects TimescaleDB. It also calls api.wheretheiss.at over HTTP.
How it runs
Trigger: On a schedule (legacy Cron node).
- HTTP Request: calls api.wheretheiss.at
- Set (Edit Fields (Set)): sets or maps fields
- TimescaleDB: uses TimescaleDB
Services it uses
HTTP calls to: api.wheretheiss.at
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Rarely used nodes in this template: n8n-nodes-base.timescaleDb
Nodes used (4)
- TimescaleDB
n8n-nodes-base.timescaleDb - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Cron
n8n-nodes-base.cron
From the author
This workflow allows you to receive updates about the positiong of the ISS and add it to a table in TimescaleDB. Cron node: The Cron node triggers the workflow every minute. You can configure the time based on your use-case. HTTP Request node: This node makes…