Webhooks & release registry

Release records, webhooks, and the pipeline state model.

Creytix Connect registry — abstract operator panel with native tool lanes

Note

The release registry is the record-keeping half of Creytix Ship — what shipped, when, and what state it's in.

Overview

Every time something ships through Creytix, it becomes a record — not just a line in a deploy log. The release registry tracks what shipped and its current state, moving through a small pipeline model as the deploy gate runs and the push completes. Webhooks let anything downstream react to a release the moment its state changes, instead of polling for updates.

How it works

A release is recorded the moment a change is queued to ship, with a starting status.
Status moves through a small state model — pending, processing, complete, or failed — as the deploy gate runs and the push goes out.
A webhook fires on state changes, so your own automation, a status dashboard, or a notification channel can react without polling.

Steps

•
Open the release registry
From the Creytix Control Panel, open Releases to see the current registry.
•
Find a release and check its state
Look up a specific release and see whether it's pending, processing, complete, or failed.
•
Point a webhook at Ship
Configure an endpoint to receive release-state notifications from Creytix Ship.
•
Confirm delivery
Trigger or wait for the next release and confirm your endpoint received the notification.

Capabilities

Release registry — a queryable record of what shipped, when, and its current state.
Pipeline state model — pending, processing, complete, failed — so you always know where a release actually is.
Webhook delivery — outbound notification when a release changes state.
History — look back at what shipped, not just what's shipping right now.

Limits & honest scope

The registry covers releases that go through Creytix Ship — it isn't a universal deploy-log aggregator for pipelines you run entirely outside the platform.