NASA n8n integrationAutomate NASA with n8n.

Browsing the whole near-Earth object dataset gives you the catalog itself, page by page, rather than a slice tied to a date. Useful when you want a local copy to query later.

• Return All: on, n8n walks every page of the dataset and hands back all the asteroids; off, it stops at Limit.
• Limit: the maximum number of asteroid records to bring back in one run, which keeps a first test small.

Here the dataset is sliced by approach date: the operation answers which asteroids come closest to Earth in a given window, with their approach details.

• Start Date: first day of the window, as YYYY-MM-DD. A workflow usually computes it, for example {{ $json.startDate }} from a Set node.
• End Date: last day of the window, same format. Left empty, the API decides the span, so set both for a predictable volume.

One object, one record. Give the node an identifier and it returns that asteroid's full entry, which is how you enrich a row you already have.

• Asteroid ID: the NASA SPK-ID of the object, a number such as 3542519. It comes from a feed or browse run, typically as {{ $json.id }}, and it is an ID, not a name.
• Include Close Approach Data: on, the response carries every recorded close approach for that object, which makes the item much larger.

NASA publishes one image with an explanation every day. This operation fetches it, either as a link or as a real file attached to the item.

• Put Output File in Field: required. The name of the binary field that will hold the image, often data, and the name your upload or email step must point at.
• Download Image: off, only the image URL comes back; on, n8n downloads the file into that field.
• Date: a past day as YYYY-MM-DD, to fetch an older picture instead of today's.

Coronal mass ejections are the large clouds of plasma the Sun throws out. This operation returns the CME events DONKI recorded over a period, with the analysis attached to each one.

• Start Date: opening day of the search window, format YYYY-MM-DD. For a daily watch, point it at yesterday.
• End Date: closing day of the window. Keep it short on a scheduled run so each execution handles a handful of events, not a year of them.

High speed streams are fast solar wind flows that reach Earth from coronal holes. The operation lists the ones catalogued in the window you ask for.

• Start Date: where the catalogue lookup begins, as YYYY-MM-DD.
• End Date: where it stops. A wider window here is common, since these streams recur with the Sun's rotation and a month of history reads better than a day.

Shocks are the pressure fronts detected as solar wind disturbances travel outward. This is the only DONKI operation in the node with filters beyond dates.

• Start Date and End Date: the observation window, both as YYYY-MM-DD.
• Location: where the shock was detected, among ALL, earth, MESSENGER, STEREO A and STEREO B. Pick earth when only near-Earth effects matter.
• Catalog: ALL, SWRC_CATALOG or WINSLOW_MESSENGER_ICME_CATALOG, depending on which source you trust for the study.

The magnetopause is the boundary of Earth's magnetic shield, and it moves when solar wind pressure rises. This operation returns the crossings DONKI logged between two days.

• Start Date: beginning of the period under review, as YYYY-MM-DD.
• End Date: end of that period. Crossings are rarer than flares, so an empty result over a short window is normal and your workflow should handle it quietly.

Rather than raw event records, this returns the written notifications DONKI publishes: the summaries and watches analysts send out when something happens.

• Start Date: first day of the notification range, as YYYY-MM-DD.
• End Date: last day of the range. A short window keeps the digest readable, since one active week produces a lot of text.

When the Van Allen belts charge up, satellites in those orbits feel it. This operation lists the enhancement events recorded in your window.

• Start Date: the earliest day to inspect, as YYYY-MM-DD.
• End Date: the latest. Since these events cluster after storms, a window that starts a few days before a known flare usually tells the more complete story.

Solar energetic particle events are the bursts of accelerated particles that arrive quickly after a strong eruption. The node returns the ones DONKI recorded.

• Start Date: opening of the window, as YYYY-MM-DD.
• End Date: closing of the window. Because particle events follow flares by hours, querying the same range as your flare run makes the two sets line up.

Flares are the sudden brightenings on the Sun, and they are the entry point most people start from. The operation hands back the flare records for a period.

• Start Date: first day to scan, as YYYY-MM-DD. On a daily schedule, an expression pointing at yesterday keeps the run rolling on its own.
• End Date: last day to scan, same format.

WSA+Enlil is the model that forecasts how solar wind and ejections propagate through the solar system. This operation returns the simulation runs, not observations.

• Start Date: earliest simulation date to retrieve, as YYYY-MM-DD.
• End Date: latest one. Runs are produced when modelers need them, so a window of several days is safer than a single date if you want something back.

Before downloading a satellite view, you can ask what exists for a location. This operation returns the available Earth assets for a point on the globe.

• Latitude and Longitude: the coordinates of the spot, decimal degrees such as 47.751076 and -120.740135.
• Date: the day you are asking about, as YYYY-MM-DD.
• Degrees: the width and height of the area in degrees, for example 0.025.

This one brings back the satellite image itself for a point on Earth, attached to the item as a file your next node can send or store.

• Put Output File in Field: required. The binary field that receives the image; reuse the same name across the workflow so upload steps stay simple.
• Latitude and Longitude: the point to photograph, for example 47.751076 and -120.740135, often coming from a row as {{ $json.lat }}.
• Date and Degrees: the day, as YYYY-MM-DD, and the size of the framed area in degrees.