Where does the earthquake data come from?

The U.S. Geological Survey (USGS), which is the standard public source for seismic events worldwide. The data is free, public, and refreshed every minute by USGS.

How fast will I see an alert after a quake?

USGS publishes new events to its public feeds about once a minute. This workflow checks every 15 minutes by default, so most alerts land within a few minutes of the event being published. You can run it more often if you need tighter timing.

Will I get spammed during aftershock sequences?

No. Aftershocks belonging to the same event sequence are grouped into a single Slack thread instead of new top-level messages, so the channel stays readable even during an active swarm.

Can I change which Slack channel gets the alerts?

Yes. The channel is a setting on the workflow. You can change it any time, or run multiple copies that post to different channels with different magnitude thresholds.

What is the PAGER alert level in the message?

PAGER is the USGS impact rating for an earthquake. It runs green, yellow, orange, red, with green meaning very little expected impact and red meaning catastrophic. The alert includes it so your team can triage at a glance.

Does this cost anything to run?

The USGS data is free and public. You only pay for the Geni runs themselves, which is a handful of cents per day at a 15-minute schedule.

Real-time earthquake alerts in Slack (USGS)

Build me an agent workflow that watches for significant earthquakes and posts contextualized alerts to a Slack channel so my ops team sees them within minutes.

Trigger: cron, every 15 minutes.

Parameters on the prompt (configurable per install):

- slack_channel: the Slack channel ID or name to post alerts in (e.g. #ops-alerts). Required.

- min_magnitude: minimum magnitude for routine alerts. Default 4.5.

- min_pager_override: the PAGER alert level (green, yellow, orange, red) that lets a sub-threshold event through anyway. Default yellow.

On each run, the agent should:

1. Use the USGS Earthquake integration's Real-time Summary Feed operation to read both the 4.5+/day GeoJSON feed and the significant/day GeoJSON feed. These are static files refreshed every minute, which is the right surface for "what just happened" (do not run a fresh catalog query on every tick).

2. Merge the two feeds and deduplicate by USGS event id. Maintain a small persistent record across runs of which event ids have already been alerted so we never re-alert the same event.

3. Apply the noise filter: an event qualifies for alerting if its magnitude is at least min_magnitude, OR its PAGER alert level is at least min_pager_override (yellow, orange, or red by default). Events that fail both checks are skipped.

4. Collapse aftershocks. If a new event looks like an aftershock of an event we've already alerted on (same general region within roughly 100 km and within ~48 hours of the parent, lower magnitude), post it as a threaded reply to the original alert message instead of a new top-level message. Track the parent Slack message timestamp alongside the parent event id so threading works across runs.

5. For each qualifying new event, use Slack's Send a Message operation to post to slack_channel. Lead with magnitude and place name (e.g. "M5.8 — 14 km SSW of Acari, Peru"). Then include depth in km, PAGER alert level (with a colored emoji: 🟢🟡🟠🔴), MMI shaking intensity if present, tsunami flag if the event has tsunami=1, and a direct link to the USGS event page (https://earthquake.usgs.gov/earthquakes/eventpage/<id>). Use Slack mrkdwn formatting (*bold*, <url|text>).

6. For aftershock threaded replies, keep the message terser: magnitude, distance/bearing from the mainshock, depth, time, and the USGS link.

Use the slack integration (user OAuth) for Send a Message, not the deprecated slack-bot integration. The USGS Earthquake integration requires no auth. Be defensive about USGS returning 204 No Content (no new events) and handle the case where a feed is briefly unreachable by skipping that tick rather than crashing.

What it does

Watches the official USGS earthquake feeds every 15 minutes and posts an alert to your chosen Slack channel for each new significant event.
Leads each alert with magnitude and place name, then adds depth, severity (PAGER green to red), shaking intensity, tsunami status, and a direct link to the USGS event page.
Suppresses noise by skipping small quakes below your minimum magnitude, unless an event has been flagged yellow or higher for impact.
Collapses aftershocks from the same sequence into a single Slack thread so your channel does not get spammed during an active swarm.

What you’ll need

A Slack workspace where you can install Geni and choose the channel that should receive alerts.
The name of the Slack channel you want alerts posted in (for example, #ops-alerts).
Your preferred minimum magnitude for routine alerts (for example, 4.5).

How to customize it

Change the channel, or have alerts go to multiple channels for different regions or severities.
Raise or lower the minimum magnitude, or tighten the rule that lets lower-magnitude but high-impact quakes still get through.
Adjust how often it checks. Every 15 minutes is the default, but you can run it more or less often.
Filter by region if you only care about quakes in a specific country, state, or radius around a location.

Use cases

Notifications & Alerts
Research & Monitoring

Earthquake alerts in Slack from USGS feeds

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts