How do I connect USGS Earthquakes to Lodol?

Authenticate USGS Earthquakes once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

USGS Earthquakes

Weather & SpaceResearch & Academia

Read the USGS Earthquake Catalog: every earthquake the USGS and its contributing networks have recorded, from this minute back through the last century. Watch the real-time feeds on a schedule, search the catalog by time, magnitude, depth, region or PAGER alert level, geo-fence a site and see how far away each event was and in which direction, count a window before you fetch it, pull the largest event of the week, or summarise a period for a digest. No API key, no sign-up and no quota.

Get Started Browse all integrations

11 actions

Actions

Steps your workflow can run in USGS Earthquakes.

Get recent earthquakesGet the earthquakes from the last hour, day, week or month from the USGS real-time feeds - the route the USGS asks automated applications to use for recent activity, because the feeds are pre-rendered and cached rather than searched on demand. Use this for anything on a schedule. Optionally keep only the events above a magnitude, or within a radius of a place, both of which are applied to the feed here at no extra cost.

Search earthquakesSearch the full USGS catalog - every earthquake back to 1900 and beyond - by time, magnitude, depth, place, alert level, felt reports and more. This is the action for a specific question about a window or a region; for watching for new activity on a schedule, use Get recent earthquakes, which the USGS asks automated applications to use instead. With nothing filled in it returns the last 30 days, and the window it actually used is always reported back.

Find earthquakes near a placeFind the earthquakes within a radius of a point - a site, an office, a customer's address - nearest first, each with how far away it was in kilometres and miles and which direction it lay. That distance is the thing a radius search leaves out: the catalog returns the events inside the circle but never says how far away any of them was, so it is worked out here. Defaults to a 100 km radius over the last 30 days.

Get an earthquake by IDLook one earthquake up by its USGS event id, for re-reading an event an earlier step found or a colleague linked to. A full event-page link is accepted in place of the bare id. Asking for a single event makes the catalog return every origin and magnitude solution it holds rather than only the preferred one, so this is also the fuller record.

Count earthquakesCount the earthquakes a search would match, without fetching any of them. One small answer however big the number, which makes it the cheap way for a schedule to ask 'was there anything?' before doing the expensive part - and the way to check a search is inside the 20,000 events one response can carry, since the catalog rejects a bigger one rather than trimming it.

Get the largest earthquakeFind the single biggest earthquake in a window, optionally within a region - the one line a weekly digest or a morning briefing wants. A quiet window is reported as 'found: false' with a message rather than as a failure, so a scheduled post can say 'nothing above M4 this week' instead of the step dying on the weeks when that is the news. Defaults to the last 7 days.

Summarize earthquake activitySummarise a window's seismic activity for a digest: how many events, how they split across the magnitude bands, the largest and the most significant, how many people felt, how many carried a tsunami flag, and the regions with the most activity. The total is exact however busy the window; the rest is computed over the events read, and 'complete' says whether those are the same set. Defaults to the last 7 days.

List catalogsList the catalogs a search can be limited to. A catalog is one authoritative collection of events - the ANSS Comprehensive Catalog, a regional network's own, a specific study. Naming none, which is the default everywhere here, gets the most preferred information about each event from whichever catalog holds it.

List contributorsList the seismic networks that contribute events - 'ak' for Alaska, 'ci' for southern California, 'us' for the USGS national operation. Every event names its own in 'network', so this is the list to choose from when filtering a search by one, or to resolve a code an event came back with.

List event and product typesList the event types, magnitude types and product types the catalog uses, in one call. Worth running once while building: the catalog is not only earthquakes - it records quarry blasts, explosions, mine collapses, sonic booms and ice quakes too, and a search that names no event type returns all of them.

Check service statusCheck whether the USGS earthquake catalog is answering, and how quickly. This is the one action that reports a problem as a value instead of failing the step, so a workflow can decide what to do about it - skip a digest, wait, or say the data is stale rather than dying halfway through. Being throttled is reported separately from being down.