---
title: Automation Webhooks
description: Learn how to configure webhooks for Capawesome Cloud Automations to receive Git events from your provider.
---

# Webhooks

Automations use webhooks to receive Git events from your provider. When you create an automation, Capawesome Cloud automatically registers a webhook on your connected Git repository. If automatic registration fails, you can configure the webhook manually.

## Automatic Setup

When you create an automation, Capawesome Cloud attempts to register a webhook on your Git repository automatically. If the registration succeeds, no further action is needed — the webhook is ready to receive events.

## Manual Setup

In some cases, automatic webhook registration may fail — for example, due to insufficient permissions or when using a self-hosted Git provider. In these cases, you can configure the webhook manually using the values provided in the **Setup** dialog.

### Access the Setup Dialog

To access the Setup dialog, navigate to the [Automations](https://console.cloud.capawesome.io/apps/_/automations){:target="_blank"} page of your app in the Capawesome Cloud Console and click the **Setup** button. The dialog displays two values:

- **Webhook URL**: The endpoint that receives Git events from your provider.
- **Webhook Secret**: A secret used to verify incoming webhook payloads.

Both values have copy-to-clipboard buttons for convenience.

### Configure Your Git Provider

Webhooks are registered automatically by Capawesome Cloud when you connect a repository through a [Git connection](../integrations/index.md). Manual setup is only needed if automatic registration fails — add a new webhook in your Git provider's settings using the **Webhook URL** and **Webhook Secret** from the Setup dialog, configured to send push events.

!!! note "Git (HTTP/S) connections"

    [Git (HTTP/S)](../integrations/git.md) connections do not support webhooks, so Automations are not available for repositories connected this way.

## Verifying the Webhook

To confirm that the webhook is working correctly:

1. Push a commit or create a tag that matches one of your automation's trigger patterns.
2. Navigate to the [Automations](https://console.cloud.capawesome.io/apps/_/automations){:target="_blank"} page and check that the automation's **Last triggered** timestamp has updated.
3. Navigate to the [Builds](https://console.cloud.capawesome.io/apps/_/builds){:target="_blank"} page and verify that a new build was created.