> 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/automate/workflows/full-webhook-examples.md).

# Full Webhook Examples

{% hint style="warning" %}
Webhook Notification Channel is getting an upgrade: meet [Webhook Destination](/automate/connected-apps/generic-webhook.md)
{% endhint %}

This section contains comprehensive examples of webhook integrations with various third-party services. These examples provide step-by-step instructions for setting up complete workflows with external systems.

## Available Examples

* [**incident.io**](/automate/workflows/full-webhook-examples/incident.io.md) - Integrate with incident.io for incident management
* [**MS Teams**](/automate/workflows/full-webhook-examples/ms-teams.md) - Send notifications to Microsoft Teams channels
* [**Email via Zapier**](broken://pages/AnUw8JjLjI9n2Uw0k24k) - Route alerts to email using Zapier
* [**Slack App with Bot Tokens**](/automate/workflows/full-webhook-examples/slack-app-for-channel-routing.md) - Route alerts to different slack channels with a single Webhook

Each example includes:

* Prerequisites and setup requirements
* Step-by-step configuration instructions
* Complete workflow YAML configurations
* Integration-specific considerations and best practices

These examples demonstrate advanced webhook usage patterns and can serve as templates for other webhook integrations.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/automate/workflows/full-webhook-examples.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.