Inbound webhooks

Create or move issues from signed requests by external systems.

Inbound webhooks are the reverse direction: an external system makes a signed request to Hilbana to create a new issue or move an existing one’s state.

What it is

Configured in Settings → Inbound webhooks (admins only). Each one points to a team (required) and a project (optional; otherwise General), and gives you a receiving URL and a secret.

What it’s for

Registering issues programmatically from forms, monitoring, CI or other tools, without using the full API.

How to use it

The external system makes a signed POST (HMAC-SHA256 with the webhook’s secret) to the receiving URL, with one of two bodies:

Create: { "action": "create", "title": "…", "description": "…", "priority": "…" }. The title is required.
Move: { "action": "move", "identifier": "DRAPPS-123", "state": "completed" }. The state is given by category (backlog, unstarted, started, completed…), not by name.

Details

Authentication is by the signature, not by a token in the URL; an invalid signature is rejected.
Each webhook has its own secret.

Related: Outgoing webhooks · Email inboxes · Issues.