[Integrations](https://spiral.ai/integrations) › [Zapier](https://spiral.ai/integrations/zapier) › [GDACS disaster alert changes](https://spiral.ai/integrations/zapier/gdacs-disaster-alert-changes)

# How to Use GDACS disaster alert changes in Zapier

Returns disaster alerts modified since a previous check. Use it to refresh an existing event collection when GDACS revises an alert, rather than collecting the whole date window again.

|  |  |
| --- | --- |
| Model | GDACS disaster alert changes |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GDACS disaster alert changes in Zapier

- Every six hours, use GDACS disaster alert changes to retrieve records modified during the previous six hours and summarize the returned events.
- Every Monday at 9am: use GDACS disaster alert changes to look this up and give me the result as a table.
- Pull the latest numbers from GDACS disaster alert changes and tell me what changed since last week.
- Check GDACS disaster alert changes and summarize what you find in three bullet points.
- Pull the newest data from GDACS disaster alert changes and give me the result as a table.

## How to set up GDACS disaster alert changes in Zapier

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send Zapier this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Add an MCP Client connection**: In Zapier open Apps, click Add connection and search for MCP Client. Fill in the form:

```text
https://api.spiral.ai/mcp
```

2. **Sign in to Spiral and approve**: Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Zapier never sees it, and you can remove it under Settings › Connected apps in the console.

3. **Run a Spiral tool in a Zap**: Add an MCP Client step to a Zap and choose the Run Tool action with your Spiral connection. Pick a tool: `discover` finds the right model for a task, `estimate_cost` prices it and `run` runs it. For example, `run` with:

```json
{
  "provider": "fal",
  "model": "fal-ai/flux/schnell",
  "input": { "prompt": "a lighthouse at dawn" },
  "wait": true
}
```

4. **Run GDACS disaster alert changes in a workflow step**: Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds GDACS disaster alert changes, prices it and runs it each time the step fires.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run GDACS disaster alert changes**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "gdacs-org/disaster-alerts/records_changes",
    "input": {
      "since": "<since>"
    }
  }'
```

Then paste one of the prompts above: Zapier finds GDACS disaster alert changes on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/zapier

## GDACS disaster alert changes tools and prices

- [GDACS global multi-hazard alerts · Records changes](https://spiral.ai/tools/alexandria/gdacs-org/disaster-alerts/records_changes) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| since |  | — | UTC timestamp, YYYY-MM-DDTHH:MM:SS (Z optional) or a date. Required unless cursor or since_hours_ago is given. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}(T[0-9]{2}:[0-9]{2}(:[0-9]{2}(\.[0-9]+)?)?)?Z?$. |
| cursor |  | — | next_cursor from the previous page. |
| eventlist |  | — | Hazard types to include. Default: all six (EQ earthquake, TC tropical cyclone, FL flood, VO volcano, DR drought, WF wildfire). |
| since_hours_ago | 1 to 8784 | — | Relative alternative to since: changes in the last N hours (computed from the runner clock, UTC). Not with since. |

## What can you do with GDACS disaster alert changes in Zapier?

Keep a recurring disaster briefing current when GDACS revises event assessments. A scheduled agent can check the catalogue, maintain an event collection, and surface relevant records for human review.

### Maintain a disaster monitoring dashboard

Check catalogue status, collect a baseline archive, search the countries being monitored, inspect selected events, and apply subsequent changes to keep the dashboard current.

### Build a reviewed annual disaster archive

Use annual status information to plan collection, gather the year's events, search for review samples, inspect their details, and incorporate later revisions before publishing the analysis.

### Prepare recurring country briefings

Maintain a dated event collection, check source status, find relevant country alerts, examine the events behind the briefing, and update the draft when GDACS revises them.

### Review exposure around public infrastructure

Build and refresh a disaster event collection, use catalogue status to check collection scope, search relevant countries, and inspect available event footprints alongside ports, airports, or other public infrastructure.

### Find revised alerts for an editorial review

Retrieve recently modified disaster records and inspect the events behind them so an editor can reassess an earlier report before making corrections.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Zapier guides](https://spiral.ai/integrations/zapier)

## GDACS disaster alert changes in other agents

- [Amp](https://spiral.ai/integrations/amp/gdacs-disaster-alert-changes)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/gdacs-disaster-alert-changes)
- [Claude](https://spiral.ai/integrations/claude-desktop/gdacs-disaster-alert-changes)
- [Claude Code](https://spiral.ai/integrations/claude-code/gdacs-disaster-alert-changes)
- [Cline](https://spiral.ai/integrations/cline/gdacs-disaster-alert-changes)
- [Codex](https://spiral.ai/integrations/codex/gdacs-disaster-alert-changes)
- [Cursor](https://spiral.ai/integrations/cursor/gdacs-disaster-alert-changes)
- [Devin](https://spiral.ai/integrations/devin/gdacs-disaster-alert-changes)
- [dots](https://spiral.ai/integrations/dots/gdacs-disaster-alert-changes)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/gdacs-disaster-alert-changes)
- [Gemini](https://spiral.ai/integrations/gemini/gdacs-disaster-alert-changes)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/gdacs-disaster-alert-changes)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/gdacs-disaster-alert-changes)
- [goose](https://spiral.ai/integrations/goose/gdacs-disaster-alert-changes)
- [Grok](https://spiral.ai/integrations/grok/gdacs-disaster-alert-changes)
- [Grok Build](https://spiral.ai/integrations/grok-build/gdacs-disaster-alert-changes)
- [Hermes](https://spiral.ai/integrations/hermes/gdacs-disaster-alert-changes)
- [Instinct](https://spiral.ai/integrations/instinct/gdacs-disaster-alert-changes)
- [Manus](https://spiral.ai/integrations/manus/gdacs-disaster-alert-changes)
- [Muse](https://spiral.ai/integrations/muse/gdacs-disaster-alert-changes)
- [Muse Code](https://spiral.ai/integrations/muse-code/gdacs-disaster-alert-changes)
- [n8n](https://spiral.ai/integrations/n8n/gdacs-disaster-alert-changes)
- [Notion](https://spiral.ai/integrations/notion/gdacs-disaster-alert-changes)
- [OpenClaw](https://spiral.ai/integrations/openclaw/gdacs-disaster-alert-changes)
- [opencode](https://spiral.ai/integrations/opencode/gdacs-disaster-alert-changes)
- [Perplexity](https://spiral.ai/integrations/perplexity/gdacs-disaster-alert-changes)
- [Raycast](https://spiral.ai/integrations/raycast/gdacs-disaster-alert-changes)
- [VS Code](https://spiral.ai/integrations/vscode/gdacs-disaster-alert-changes)
- [Windsurf](https://spiral.ai/integrations/windsurf/gdacs-disaster-alert-changes)

## More Zapier guides

- [Federal Court of Appeal decision text](https://spiral.ai/integrations/zapier/federal-court-of-appeal-decision-text)
- [GDACS disaster alert search](https://spiral.ai/integrations/zapier/gdacs-disaster-alert-search)
- [Federal Court of Appeal decision search](https://spiral.ai/integrations/zapier/federal-court-of-appeal-decision-search)
- [GDACS disaster catalogue status](https://spiral.ai/integrations/zapier/gdacs-disaster-catalogue-status)
- [Federal Court of Appeal decision listings](https://spiral.ai/integrations/zapier/federal-court-of-appeal-decision-listings)
- [GDACS disaster event archive](https://spiral.ai/integrations/zapier/gdacs-disaster-event-archive)

## Questions about GDACS disaster alert changes in Zapier

**Can Zapier use GDACS disaster alert changes?**

Yes. Add Spiral to Zapier as an MCP server, and Zapier can find and run GDACS disaster alert changes like any built-in tool.

**How much does GDACS disaster alert changes cost in Zapier?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Zapier plan is separate.

**Do I need an Alexandria account to use GDACS disaster alert changes in Zapier?**

No. Spiral runs GDACS disaster alert changes on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GDACS disaster alert changes in Zapier?**

About two minutes: add an MCP Client connection, then sign in to Spiral and approve, then run a Spiral tool in a Zap.

**Does Zapier wait while GDACS disaster alert changes runs?**

GDACS disaster alert changes runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.

**Does GDACS provide confirmed disaster damage totals?**

GDACS calculates potential impact using hazard characteristics, population exposure, and vulnerability. Its terms require confirmation before notifications or automatic impact estimates are used for decisions.

**How fresh is GDACS information?**

GDACS describes its notifications as near-real-time, but explicitly gives no guarantee of completeness or timeliness. A recent retrieval does not establish that every relevant event or revision is already present.

**What does an active event mean on the GDACS homepage?**

The MHEWS homepage requires an update within the last four days, except for droughts, where the window is ten days. That label reflects recent monitoring activity rather than proof that a hazard has ended.

**Can a GDACS search return more than 100 events?**

The upstream search returns the first 100 results and supports pagination. A single result page should not be treated as the full historical collection.

**Does GDACS cover tropical cyclones outside the Atlantic?**

Yes. GDACS documents worldwide tropical cyclone coverage using NOAA and Joint Typhoon Warning Center bulletins.

