Receive updates of the position of the ISS every minute
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Function (legacy), Cron. 2 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). It uses only n8n's built-in nodes. 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
- Function: runs custom JavaScript (legacy Function node)
HTTP calls to: api.wheretheiss.at
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Function (legacy) in Function: replace with Code node, mode 'Run Once for All Items'.
- Cron: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Function | Code node, mode 'Run Once for All Items' |
| Cron Cron | Schedule Trigger |
Nodes used (4)
- Function
n8n-nodes-base.function - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Cron
n8n-nodes-base.cron
From the author
This workflow demonstrates the use of static data in n8n. The workflow is built on the concept of polling. 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 an…