> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/registries/webhooks.md).

# Webhooks

Overview of Artifact Registry webhooks, covering the two event types, package type support, payload URL requirements, and common automation patterns.

Webhooks in Harness Artifacts send HTTP POST requests to a URL you specify whenever an artifact event occurs. Use webhooks to integrate registry activity into CI/CD pipelines, security scanners, notification systems, or any HTTP-capable service.

## What you will learn from this topic

* The two artifact events that trigger webhooks
* Which package types support webhooks
* Common use cases for webhook-driven automation

## Webhook events

Artifact Registry fires webhooks on two events:

| Event                 | When it fires                                                                                                                |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Artifact Creation** | When an artifact version is pushed to a registry, or when an upstream proxy caches a version fetched from an external source |
| **Artifact Deletion** | When an artifact version is deleted from a registry or removed from an upstream proxy cache                                  |

You can subscribe a webhook to one event, both, or all events using the **Send me everything** option.

### Upstream proxy events

Artifact Creation events fire for upstream proxy registries when a version is fetched from the external source and cached. The following formats support upstream proxy webhook events: Docker, Maven, npm, Python (PyPI), and NuGet.

### Cosign artifact filtering

Webhook triggers automatically filter out Cosign signature (`.sig`) and attestation (`.att`) OCI artifacts. Only the original image push fires an event. This prevents duplicate pipeline executions from auxiliary signing artifacts that are pushed alongside container images.

## Package type support

Webhooks are supported for all registry formats except **Raw**. If you need event-driven automation for raw files, use a lifecycle rule or poll the registry using the API.

## Webhook location

Webhooks are managed from the **Webhooks** tab on each registry. Each registry has its own independent webhook list.

## Use cases

Webhooks enable a range of automation patterns:

* **Automated deployment**: trigger a Harness CD pipeline when a new image is pushed, so the latest version deploys automatically to staging.
* **Security scanning**: call an external scanner when a new artifact is cached through an upstream proxy.
* **Notifications**: post a message to a Slack channel or ticketing system when an artifact is published or deleted.
* **Audit and compliance**: send artifact events to a log aggregation service to build a tamper-evident push history.
* **Cleanup automation**: trigger downstream jobs when an artifact version is removed.

## Payload URL requirements

The payload URL you configure must be:

* A valid URL starting with `http://` or `https://`
* Publicly reachable from Harness: localhost, loopback, private (RFC 1918), and link-local addresses are rejected
* Not pointing to a cloud metadata endpoint (for example, `169.254.169.254`)

Harness sends webhook requests directly, without routing through a Harness Delegate.

## Next steps

* [Create a webhook](https://developer.harness.io/artifact-registry/3.0/registries/webhooks/create-a-webhook.md)
* [Webhook payload reference](https://developer.harness.io/artifact-registry/3.0/registries/webhooks/webhook-payload-reference.md)
