The flow
Starts it 1Service 15
The steps in the order they run, from what starts it.
- 1Get many asteroid neosNasa ToolService
- 2Get an asteroid neo feedNasa ToolService
- 3Get an asteroid neo lookupNasa ToolService
- 4Get the astronomy picture of the dayNasa ToolService
- 5Get a DONKI coronal mass ejectionNasa ToolService
- 6Get a DONKI high speed streamNasa ToolService
- 7Get a DONKI interplanetary shockNasa ToolService
- 8Get a DONKI magnetopause crossingNasa ToolService
- 9Get a DONKI notificationsNasa ToolService
- 10Get a DONKI radiation belt enhancementNasa ToolService
- 11Get a DONKI solar energetic particleNasa ToolService
- 12Get a DONKI solar flareNasa ToolService
- 13Get a DONKI wsa enlil simulationNasa ToolService
- 14Get Earth assetsNasa ToolService
- 15Get Earth imageryNasa ToolService
- 16NASA Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 16
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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.
Before you run itNothing 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.