LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
    • groundcover MCP
      • Configure groundcover's MCP Server
      • Getting-started Prompts
      • Real-world Use Cases
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Saved Views
    • Issues
    • Role-Based Access Control (RBAC)
    • Remote Access & APIs
      • Service Accounts
      • API Keys
      • APIs
      • Ingestion Keys
      • Datasource API Keys
      • Grafana Service Account Token
    • groundcover Terraform Provider
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Using KEDA autoscaler with groundcover
    • Fleet Manager
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
      • Send groundcover Alerts to Email via Zapier
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • Prerequisites
  • Step 1: Create a Webhook Integration in groundcover
  • Step 2: Create a Zapier Webhook-to-Email Workflow
  • Step 3: Create a Workflow in groundcover
  • Step 4: Test the Flow
Export as PDF
  1. Integrations
  2. Workflow Integrations

Send groundcover Alerts to Email via Zapier

Last updated 24 days ago

This guide shows how to route groundcover alerts to email using . Since groundcover supports webhook-based alerting, and Zapier can receive webhooks and send emails, you can easily set up this workflow without writing code.


Prerequisites

  • A groundcover account with access to the Workflows tab.

  • A Zapier account (free plan is sufficient).

  • An email address where you want to receive alerts.


Step 1: Create a Webhook Integration in groundcover

  1. Go to Settings → Integrations.

  2. Click Create Integration.

  3. Choose Webhook as the type.

  4. Enter a name like zapier_email_integration.

  5. Paste your Zapier Catch Hook URL (you’ll get this in Step 2 below).

  6. Save the integration.


Step 2: Create a Zapier Webhook-to-Email Workflow

Create a Webhook Trigger

  1. Click "Create Zap".

  2. Set Trigger:

    • App: Webhooks by Zapier

    • Event: Catch Hook

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

Step 3: Create a Workflow in groundcover

  1. Go to the Workflows section in your groundcover.

  2. Create a Notification Workflow with the integration we created in step 1.

  3. Edit the worflow YAML and use the following structure:

workflow:
  id: emails
  description: Sends alerts to Zapier webhook (for email)
  triggers:
  - type: alert
    name: emails
  consts:
    severity: keep.dictget( {{ alert.annotations }}, "_gc_severity", "info")
    title: keep.dictget( {{ alert.annotations }}, "_gc_issue_header", "{{ alert.alertname }}")
    issue_url: https://app.groundcover.com/monitors/issues?backendId={{ alert.labels.backend_id }}&selectedObjectId={{ alert.fingerprint }}
    monitor_url: https://app.groundcover.com/monitors?backendId={{ alert.labels.backend_id }}&selectedObjectId={{ alert.labels._gc_monitor_id }}
    silence_url: https://app.groundcover.com/monitors/create-silence?keep.replace(keep.join({{ consts.redacted_labels }}, "&", "matcher_"), " ", "+")
    redacted_labels: keep.dict_pop({{ alert.labels }}, "_gc_monitor_id", "_gc_monitor_name", "_gc_severity", "backend_id", "grafana_folder", "_gc_issue_header")
  actions:
  - name: <<THE_NAME_OF_YOUR_WORFLOW>>
    provider:
      config: "{{ providers.<<THE_NAME_OF_YOUR_INTEGRATION>> }}"
      type: webhook
      with:
        body:
          alert_name: "{{ consts.title }}"
          severity: "{{ consts.severity }}"
          issue_url: "{{ consts.issue_url }}"
          monitor_url: "{{ consts.monitor_url }}"
          silence_url: "{{ consts.silence_url }}"

Step 4: Test the Flow

  1. Trigger a test alert in groundcover.

  2. Check Zapier to ensure the webhook was received.

  3. Confirm the email arrives with the right content.

Go to .

Zapier
Zapier