Space Weather Events
nasa.donki_events
ActionBusiness appsconnection required
Calls the NASA API with the connection's credentials.
Read one DONKI space-weather event service for a date range.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- NASA
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url, images_base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
event_type Which DONKI service to read: coronal mass ejections, geomagnetic storms, interplanetary shocks, solar flares, solar energetic particles, magnetopause crossings, radiation belt enhancements, high speed streams, or WSA+Enlil simulations. | string | Yes | — | one of "CME", "GST", "IPS", "FLR", "SEP", "MPC", "RBE", "HSS", "WSAEnlilSimulations" | — |
start_date First day to read events from; NASA uses 30 days ago when it is blank (seven days for WSA+Enlil simulations). | string | No | — | matches ^\d{4}-\d{2}-\d{2}$ | 2016-09-01 |
end_date Last day to read events to; NASA uses today when it is blank. | string | No | — | matches ^\d{4}-\d{2}-\d{2}$ | 2016-09-30 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"end_date": "2016-09-30",
"start_date": "2016-09-01"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
event_type The DONKI service that was read. | string | — |
events The events DONKI returned, as returned. | array | — |
count How many events are in this response. | number | — |
{
"count": 0,
"event_type": "",
"events": []
}See Space Weather Events run in a workflow.
In a technical demo we add the NASA connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.