> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/integrations/connected-apps/generic-webhook/email-via-zapier.md).
# Email via Zapier
This guide shows how to route groundcover alerts to email using [Zapier](https://zapier.com). Since groundcover supports webhook-based alerting via a [Generic Webhook](/integrations/connected-apps/generic-webhook.md) Destination, and Zapier can receive webhooks and send emails, you can set up this flow without writing code.
#### Prerequisites
* A groundcover account with access to **Integrations โ Destinations** and **Monitors โ Notification Routes**.
* A Zapier account (free plan is sufficient).
* An email address where you want to receive alerts.
***
#### Step 1: Create a Zapier Webhook-to-Email Zap
**Create a Webhook Trigger**
1. Go to [Zapier](https://zapier.com).
2. Click **"Create Zap"**.
3. Set **Trigger**:
* App: `Webhooks by Zapier`
* Event: `Catch Hook`
4. Copy the **Webhook URL** (e.g. `https://hooks.zapier.com/hooks/catch/...`) โ you'll use this in groundcover.
***
**Configure the Email Step**
1. Set **Action**:
* App: `Email by Zapier`
* Event: `Send Outbound Email`
2. Configure the email:
* **To**: your email address
* **Subject**:
```
๐จ New groundcover Alert ๐จ
```
* **Body**:
```
๐ Alert Title: {{alert_name}}
๐ผ Severity: {{severity}}
๐ Links:
- ๐งน Issue: {{issue_url}}
- ๐ Monitor: {{monitor_url}}
- ๐ Silence: {{silence_url}}
```
{% hint style="info" %}
The `{{alert_name}}`, `{{severity}}`, and URL fields are populated from the webhook payload keys you define in the Generic Webhook custom payload below. After you send a test notification from groundcover, you can map these fields in Zapier from the Catch Hook sample data.
{% endhint %}
***
#### Step 2: Create a Generic Webhook Destination in groundcover
1. Go to **Integrations โ Destinations**.
2. Create a new Generic Webhook.
3. Give it a name like `zapier_email`. This name will be used when you attach the Destination to a [Notification Route](/use-groundcover/monitors/notification-routes.md).
4. Set the **Webhook URL** to the Zapier Catch Hook URL from [Step 1](#step-1-create-a-zapier-webhook-to-email-zap).
5. Keep the HTTP method as `POST`.
6. Open **Custom Payload** and use the following example. It uses [predefined variables](/integrations/connected-apps/generic-webhook/using-predefined-variables.md) so Zapier receives the fields your email step expects:
```json
{
"alert_name": "{{ summary }}",
"severity": "{{ severity }}",
"issue_url": "{{ urls.issue }}",
"monitor_url": "{{ urls.monitor }}",
"silence_url": "{{ urls.silence }}"
}
```
7. Optionally click **Test** to send a sample payload to Zapier, then save the Destination.
***
#### Step 3: Create a Notification Route
1. Go to **Monitors โ Notification Routes**.
2. Click **Create Notification Route**.
3. Give the route a name (e.g. `email-alerts`).
4. Set a **Scope** for which monitors should trigger this route (e.g. `*` for all monitors, or a narrower filter).
5. Add a **Rule**:
* **Status**: `Firing` (and optionally `Resolved`, if you also want resolution emails)
* **Destinations**: select the `zapier_email` Generic Webhook Destination from Step 2
6. Save the route.
For more details on scopes and rules, see [Notification Routes](/use-groundcover/monitors/notification-routes.md).
***
#### Step 4: Test the Flow
1. Use the **Test** button on the Generic Webhook Destination, or trigger a real alert from a monitor in scope.
2. In Zapier, confirm the Catch Hook received the payload and that the email fields map correctly.
3. Confirm the email arrives with the expected title, severity, and links.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.groundcover.com/integrations/connected-apps/generic-webhook/email-via-zapier.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.