Send location updates of the ISS every minute to a table in Google BigQuery
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 Google BigQuery. 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
- Google BigQuery: uses Google BigQuery
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.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Nodes used (4)
- Google BigQuery
n8n-nodes-base.googleBigQuery - 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 send position updates of the ISS every minute to a table in Google BigQuery. Cron node: The Cron node will trigger the workflow every minute. HTTP Request node: This node will make a GET request to the API…