Screens

Webhooks

Let other systems know when a release is submitted, published or rejected, so they can react on their own.

What they’re for

A webhook is a web address of yours that Stoaken calls when something happens. Use one to rebuild your app when a release is published, post in a team chat when one is waiting for review, or update a dashboard.

  • Release submitted for review
  • Release published
  • Release rejected

Each message is small and signed, so your system can check it really came from Stoaken. It carries ids, not tokens: fetch the details from the API.

Adding one

  1. Pick the Brand. Webhooks are per Brand, up to 10 each, and need a Brand Admin.
  2. Add a webhook with its https address and an optional description.
  3. Copy the signing secret straight away: it’s only shown once. Your system uses it to check each message.
  4. Send test sends a sample event, so you can check it arrives.

Tip: Use one address per job (CI, a chat bot, a dashboard). Each gets its own secret, and one failing doesn’t affect the others.

Keeping them healthy

  • Recent deliveries shows each call, and whether it worked. Failed ones are retried for about a day.
  • Disable pauses a webhook without deleting it.
  • Rotate secret gives it a new secret. For a while, messages carry both signatures, so you have time to update your system.

Good to know: Webhooks are part of the Team plan.

Looking for the API, CLI or AI agents? They’re in the developer docs.