Email via Zapier

This guide shows how to route groundcover alerts to email using Zapier. Since groundcover supports webhook-based alerting via a Generic Webhook 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.

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}}

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.

---

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.

4. Set the Webhook URL to the Zapier Catch Hook URL from Step 1.

5. Keep the HTTP method as POST.

6. Open Custom Payload and use the following example. It uses predefined variables so Zapier receives the fields your email step expects:

{
  "alert_name": "{{ summary }}",
  "severity": "{{ severity }}",
  "issue_url": "{{ urls.issue }}",
  "monitor_url": "{{ urls.monitor }}",
  "silence_url": "{{ urls.silence }}"
}

1. 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.

---

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.