May’d It
NOAA Space Weather Alert Monitor — illustrative workflow

DATA TOOLS / public records

NOAA Space Weather Alert Monitor

Export official NOAA space-weather bulletins for satellite, radio and grid research. Filter product IDs or message text, preserve source wording and compare saved bulletin changes.

JSON / CSV outputLimited permissionsSource: maydit/noaa-space-weather-alert-monitor

FROM SOURCE TO A USEFUL RESULT

A practical workflow

Choose this tool when…

Satellite and communications analysts, GNSS-dependent operations researchers, grid-risk reporting teams and automation builders who need traceable official bulletins.

titleproductIdmessageCodeserialNumberissuedAtobservationAgeHourssourceFreshnesscomparisonStatussourceUrl

Which official NOAA space-weather bulletins matter to our operational watchlist?

Run the default to review three recent bulletins and their issue timestamps. Filter by an exact source product ID or a literal term such as radio or geomagnetic. Join the full official bulletin to your own incident workflow; use comparisons to spot source text changes.

Check the fit and source limits

The retained feed is not a complete historical archive and its window can change. A bulletin in the feed is not necessarily still active; validity, extensions and cancellations remain in the original message. No independent hazard ranking, predicted business loss or operating recommendation is generated. Official sources and established emergency channels take precedence for safety decisions.

Download this workflow as Markdown · Configure a small first run

REAL RUN · DATED EVIDENCE

See an actual saved result

Captured 2026-11-21. Selected columns from one saved row. Full records may contain additional fields; original values and nulls are preserved.

{
  "recordId": "noaa-swpc:K04W:2026-11-19T01:18:16.670Z",
  "title": "EXTENDED WARNING: Geomagnetic K-index of 4 expected",
  "productId": "K04W",
  "messageCode": "WARK04",
  "serialNumber": "5457",
  "issuedAt": "2026-11-19T01:18:16.670Z",
  "observationAgeHours": 67.06,
  "sourceFreshness": "issued_within_72_hours",
  "comparisonStatus": "not_requested",
  "sourceUrl": "https://services.swpc.noaa.gov/products/alerts.json",
  "url": "https://services.swpc.noaa.gov/products/alerts.json",
  "observedAt": "2026-11-21T20:21:47.727Z"
}

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health. Run reference: pxhYfztsQq0anN2Zv. Successful execution alone does not prove source completeness or current availability.

START SMALL

Example input

Historical evidence for this exact JSON was recorded 2026-11-21 on its original build. This is not a fresh source-availability test. Adjust targets and dates for your use case. Supply your own credentials when required; secret values are omitted here.

{
  "maxResults": 3,
  "comparePrevious": false
}
Download input.json

CHOOSE A STARTING POINT

3 ready-to-use inputs

Pick a focused example, copy or download its JSON, then review the inputs and current pricing in your own Apify account. Downloading a configuration does not start a run.

Default input · Input schema · Saved output capture

Read three recent NOAA space-weather bulletins

Retrieve three recent official bulletins with unchanged message text, issue times, product IDs and source links.

{
  "maxResults": 3,
  "comparePrevious": false
}

Saved run evidence: 2026-11-21 UTC · 3 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Find radio-related NOAA bulletins

Filter the retained official feed for the literal word radio. This does not independently rank severity or current validity.

{
  "messageContains": "radio",
  "maxResults": 3,
  "comparePrevious": false
}

Saved run evidence: 2026-11-21 UTC · 3 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Compare K04W geomagnetic bulletins

Track the latest K04W source bulletins. The first run establishes a baseline; issue timestamps remain distinct from observation time.

{
  "productIds": [
    "K04W"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "geomagnetic-bulletins"
}

Saved run evidence: 2026-11-21 UTC · 3 saved rows. This is a historical check, not live data or a guarantee that every query will succeed today.

Download all example inputs and evidence references

A CLEAR DATA CONTRACT

Inputs you can configure

FieldTypeMeaning
productIdsarray

Optional exact IDs such as K04W. Up to 20 product IDs. Leave empty to include all source bulletin products.

messageContainsstring

Optional case-insensitive literal text, for example radio or geomagnetic. This filters official message text, not an AI severity judgement.

maxAgeHoursinteger

0 disables the age filter. Otherwise include source issue times within this many hours. The live retained feed is not a complete archive.

maxResultsinteger

Save the latest matching window of 1–100 records. Default is three. The source coverage report describes records outside the selection.

maxRunSecondsinteger

30–120 seconds including source, output and comparison. Each request is bounded to 20 seconds; the platform timeout can stop sooner.

comparePreviousboolean

Compare the same selection and snapshot name with prior complete saved observations. The first run establishes a baseline; missing records are never inferred removed.

onlyChangesboolean

Enables comparison. An unchanged repeat can correctly return zero rows. Source failures and partial runs cannot advance the baseline.

snapshotNamestring

1–80 letters, digits, underscores or hyphens. Selection settings also separate history. Run the same snapshot sequentially.

Output fields

titleproductIdmessageCodeserialNumberissuedAtobservationAgeHourssourceFreshnesscomparisonStatussourceUrl

These are the columns in the default dataset view. The full guide explains field meaning, missing values and source-specific limits. JSON preserves nested data; CSV is useful for flat columns.

Input schema JSON

KNOW THE COST

Event pricing

Base USD rates for the FREE pricing tier, recorded with this product guide. Plan discounts and future pricing changes may apply. Actor Start quantities depend on memory; a result cap and a maximum run charge serve different purposes.

EventUSD per eventWhat is charged
Actor Start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Saved observation$0.002One validated observation confirmed saved to the dataset.

BUILD A REVIEWED WORKFLOW

Use this with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

Parallel research context

Place official space-weather advisories beside separately reported vendor incidents.

  1. Review issue times, parsed validity and the original NOAA message.
  2. Run the vendor incident monitor against selected supported status feeds.
  3. Present the observations side by side for operator review with their source links.

Temporal overlap does not establish causation, local disruption or an active incident. Official operator instructions take precedence.

Read the companion guide →

Parallel research context

Build a broader source-labeled situational-awareness dashboard.

  1. Export NOAA space-weather messages and their issue times.
  2. Run GDACS separately for its supported terrestrial disaster alerts.
  3. Keep event type, validity, location scope and source explicit in the combined dashboard.

NOAA space-weather products and GDACS events have different severity scales and geographic scope. Neither feed is a substitute for emergency services.

Read the companion guide →

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Source contract captured from build 1.0.1. Presentation refreshed 2026-11-21. Example outputs retain their original sample context; they are not live results.

NOAA Space Weather Alert Monitor

Export official NOAA space-weather bulletins for satellite, radio and grid research. Filter product IDs or message text, preserve source wording and compare saved bulletin changes.

Built for: Satellite and communications analysts, GNSS-dependent operations researchers, grid-risk reporting teams and automation builders who need traceable official bulletins.

Start with three real observations

Run the default input to collect a small, traceable source window. No source API key, login, proxy or paid source subscription is required. The Actor exports actual public source records and reports source failures without creating paid diagnostic rows.

{
  "maxResults": 3,
  "comparePrevious": false
}

Open the dataset for JSON/CSV, SUMMARY for coverage and RUN_REPORT for a readable result. A successful bounded run does not prove the full source universe was collected.

Three practical recipes

Read three recent NOAA space-weather bulletins

Retrieve three recent official bulletins with unchanged message text, issue times, product IDs and source links.

{
  "maxResults": 3,
  "comparePrevious": false
}

Filter the retained official feed for the literal word radio. This does not independently rank severity or current validity.

{
  "messageContains": "radio",
  "maxResults": 3,
  "comparePrevious": false
}

Compare K04W geomagnetic bulletins

Track the latest K04W source bulletins. The first run establishes a baseline; issue timestamps remain distinct from observation time.

{
  "productIds": [
    "K04W"
  ],
  "maxResults": 3,
  "comparePrevious": true,
  "snapshotName": "geomagnetic-bulletins"
}

Understand the result

Each row preserves the official message text, productId, messageCode, source serialNumber when provided and UTC issuedAt. title is the first nonempty source line after Issue Time. No independent severity, impact probability or hazard score is invented.

observationAgeHours is age at collection; sourceFreshness distinguishes issue times within or beyond 72 hours, a transparent display threshold rather than a NOAA service guarantee. activeStatus remains not_inferred: an old warning, extension or cancellation can remain in the feed. Read the complete message for valid-from/until text and consult the official product page and NOAA scale explanations. This feed is not a historical archive.

productIds filters exact official IDs. messageContains performs case-insensitive literal text matching. maxAgeHours:0 turns off age filtering; another value applies it to the source issue timestamp. maxResults selects the latest matching bulletins, ordered by issue time. SUMMARY reports the newest/oldest feed issue time and matching count. A valid empty filter result is not a source error.

Output Purpose
recordId, sourceUrl Stable source identity and a link to the official data.
observedAt Retrieval time, separate from source issuance/publication.
comparisonStatus, changedFields, previous New, changed or unchanged source fields on requested comparisons.
SUMMARY Selected coverage, source errors, limits and history status.

Changes you can trust

Run the same selection and snapshotName sequentially with comparePrevious:true. The first complete run establishes a baseline in the named noaa-space-weather-alert-monitor-history store. onlyChanges:true also enables comparison and can correctly emit zero rows on unchanged repeats. Observation time and age alone never create changed records.

History advances only after confirmed output from a complete selected window. Source errors, interrupted output, exhausted charge allowance, deadlines and concurrent history writers prevent baseline replacement. Prior records are preserved; absent source records never imply removals, cancellations or a resolved operational condition. This Actor does not schedule itself or send alerts automatically; use your own saved task, schedule or integration.

Use with other Mayd It Actors

  • Vendor Incident Feed Monitor: Correlate official space-weather bulletins with your vendors’ published incidents without inferring causation.
  • GDACS Disaster Alert Monitor: Keep terrestrial disaster alerts and space-weather bulletins in separate, source-labelled operational feeds.

Keep source identities and timestamps when joining datasets. Correlation is a research observation, not proof of causation.

Pricing and bounds

Standard event pricing: $0.002 per confirmed saved observation, plus $0.00005 Actor Start. Three rows total $0.00605 in Actor event charges. Plan discounts and any applicable Apify platform charges are separate. A comparison with zero changed rows can still incur start/platform usage. Reports and errors are never paid dataset rows. Set a maximum total charge in Run options.

The default is three rows with a 60-second whole-run budget (30–120 seconds allowed). Each official request has a 20-second timeout and a 2 MiB response cap, within the remaining deadline. A 502/503/504 can receive one bounded retry after 500 ms; access denials, rate limits, malformed data and exhausted budgets are not bypassed. The actual platform timeout is also respected. Maximum output is 100 bulletins from the retained official feed.

Source limits and provenance

  • The retained feed is not a complete historical archive and its window can change.
  • A bulletin in the feed is not necessarily still active; validity, extensions and cancellations remain in the original message.
  • No independent hazard ranking, predicted business loss or operating recommendation is generated.
  • Official sources and established emergency channels take precedence for safety decisions.

Official source documentation · Source data and interpretation · Source field definitions

Source: NOAA/NWS Space Weather Prediction Center. Independent of and not endorsed by NOAA or NWS. Preserve the original message and timestamps when redistributing. This tool is not an emergency alerting service and must not be the sole source for safety-critical decisions.

Report reproducible issues in the Actor’s Issues tab with a non-sensitive input and run link.

Companion workflows

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

Vendor Incident Monitor - Public Outage Feeds

Place official space-weather advisories beside separately reported vendor incidents.

  1. Review issue times, parsed validity and the original NOAA message.
  2. Run the vendor incident monitor against selected supported status feeds.
  3. Present the observations side by side for operator review with their source links.

Temporal overlap does not establish causation, local disruption or an active incident. Official operator instructions take precedence.

GDACS Disaster Alert Monitor - Event Revisions

Build a broader source-labeled situational-awareness dashboard.

  1. Export NOAA space-weather messages and their issue times.
  2. Run GDACS separately for its supported terrestrial disaster alerts.
  3. Keep event type, validity, location scope and source explicit in the combined dashboard.

NOAA space-weather products and GDACS events have different severity scales and geographic scope. Neither feed is a substitute for emergency services.