> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# SEC Data Automation with Zapier

> Send signed SEC filing-monitor events to Zapier and turn matching filings into rows, messages, or review tasks.

Use Zapier to route SEC filing matches into an existing operating workflow. The reliable boundary is simple: SEC API delivers a signed `monitor.match` event; Zapier stores or routes the normalized filing fields; the next human or system can follow the source filing.

## Set up the connection

1. In Zapier, create a Zap with **Webhooks by Zapier: Catch Hook** and copy the HTTPS hook URL.
2. In the signed-in [SEC API dashboard](https://secapi.ai/app/webhooks), add that URL as an organization endpoint and subscribe it to `monitor.match`.
3. Create the monitor in the same dashboard. A useful first monitor has a focused query, form filter, and a small ticker list.

Webhook and monitor configuration are human-authenticated organization actions. They require the dashboard's WorkOS session; an API key cannot create, edit, test, or delete them.

## Map a filing match

Use these fields in a Zapier action:

| Field                       | Use it for                        |
| --------------------------- | --------------------------------- |
| `data.monitor.name`         | Alert and routing label           |
| `data.matches[].ticker`     | Company filter or destination key |
| `data.matches[].form`       | Form-specific logic               |
| `data.matches[].filingDate` | Deadline or recency logic         |
| `data.matches[].htmlUrl`    | Link to the source filing         |

Use the dashboard's test-delivery action to teach Zapier the payload. It sends `webhook.test`; real filing alerts send `monitor.match` on the scheduled monitor sweep.

## Validate a configured monitor

```bash theme={null}
curl -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/monitors/MONITOR_ID/matches?limit=10"
```

The API key is intentionally limited to these data reads. Keep the source URL with the Zapier row or task so reviewers can inspect the filing that caused the alert.

## Read next

* [Monitor SEC filing events](/monitors)
* [Build a filing monitor](/tutorials/build-filing-monitor)