Webhooks
A webhook sends an event from Jaah to a URL you own, as it happens: a task finished, a task is waiting for an
answer, a pull request merged. Your system receives an HTTPS POST with a JSON body, signed with a secret
only you and Jaah know, so it can trust the request came from Jaah. Use it to open a ticket when a task
fails, post to your team's chat when a pull request merges, or start a deploy when work is done, without
anyone watching the console.
Webhooks live under Settings › Integrations › Webhooks. Only your organization's Owners and Admins see them, and only while your plan includes webhooks.
Where webhooks fit
The events a webhook sends come from tasks and the pull requests they open. A webhook carries them out to a program; notifications carry news to a person instead, in the console or on email, Slack or Telegram. An automation with a Webhook trigger works the other way round: another system calls Jaah, and Jaah files a task.
Pages in this section
- How webhooks work — endpoints, events and signing secrets, an endpoint's life from Enabled to deleted, and how a delivery goes from Queued to Delivered or Failed.
- Receive events with webhooks — create an endpoint, choose its events, verify each delivery's signature, rotate the secret, read the delivery log and redeliver.
- Fix a failing webhook — read why deliveries fail, check the fix with Send test, and redeliver what was missed.
- Move a webhook to a new URL — point an endpoint at a new receiver without losing events, and keep or rotate its secret.
- Change which events a webhook sends — add or drop an endpoint's events, and limit it to some projects or open it to all.
- Send a project's events to its own receiver — give one project its own endpoint and take it off a shared one, with no gap in between.
- Replace a webhook signing secret — rotate the secret after a leak or on a schedule, move your receiver to it, and check deliveries still arrive.
- Pause a webhook — stop an endpoint sending while your receiver is down, then turn it back on and check it with Send test.
- Delete a webhook — remove an endpoint you no longer need, and retire its receiver and signing secret.
- Open a ticket when a task fails — send failed and waiting tasks to a receiver that files a ticket in your tracker.
- Start a deploy when a pull request merges — send merged pull requests to a receiver that deploys the merged commit.
- Ask for a review when a task opens a pull request — send each new pull request to a receiver that asks your team to review it.
- Post to a team chat when a task finishes — send finished tasks to a receiver that posts their title and link in your team's chat channel.
- Record task activity in your own system — send every task event to a receiver that keeps its own history for your reports.
- Review your organization's webhooks — go through every endpoint, check where it sends, what it sends and whether it still delivers, and retire the ones nobody needs.
- Find out who changed a webhook — see in Audit who created, edited, tested, rotated or deleted an endpoint, and what changed.
What each screen shows is in the console reference: Webhooks. The event types you can choose are listed in the event catalog. Every endpoint action is also a call to the Jaah API.