The flow
Starts it 1Logic 9Service 6
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get ISS PositionHttp RequestService
- 3Calculate Distance and DirectionCodeLogic
- 4Is ISS Overhead?IfLogic
- 5Get Local WeatherHttp RequestService
- 6ISS Not OverheadSetLogic
- 7Analyze Observation ConditionsCodeLogic
- 8Can Observe?IfLogic
- 9Format Alert (Good Conditions)CodeLogic
- 10Format Alert (Poor Conditions)CodeLogic
- 11Merge MessagesMergeLogic
- 12Get ISS Crew InfoHttp RequestService
- 13Add Crew InformationCodeLogic
- 14Send to DiscordDiscordService
- 15Send to TelegramTelegramService
- 16Send Email via GmailGmailService
How it's built
- Starts on
- A clock
- Steps
- 16, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Discord, Gmail, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Discord, Gmail and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.