Monitor New FEMA Disaster Declarations

A declaration monitor is different from a weather alert. Its job is to detect new official administrative records, preserve their details, and route them to the teams that manage response, coverage, grants, or reporting. The FEMA Disaster Scraper provides the structured source for that workflow.

Configure a rolling overlap window

Choose the states you serve and request a recent period with enough overlap for corrections.

{"states":["TX","LA","FL"],"fromDate":"2026-01-01","maxResults":250}

Save this configuration as an Apify Task and schedule it daily. In the receiving system, upsert by id and compare the new payload with the stored version. Trigger a new-declaration notification only for unseen IDs, while logging updates to existing records separately. This prevents repeated alerts when the rolling window returns the same declarations.

Route alerts with the disaster number, title, state, designated area, declaration type, declaration date, and official FEMA link. Program flags can change the responsible internal team, but a false or null value should not be turned into an eligibility conclusion.

Monitor pipeline health with three checks: the Task completed, the source refresh timestamp is plausible, and the latest expected state data is present. Zero results can be valid for a narrow window, so absence alone is not proof of failure.

Keep the operational distinction clear. This feed describes federal declarations; it does not predict hazards, replace local emergency messages, or determine an individual's assistance eligibility. Link every notification to official guidance.