Skip to content

Manage webhooks

You will learn how to create webhook subscriptions, save the signing secret, monitor delivery health, and replay failed deliveries.

Tixio POSTs events to your HTTPS endpoint so your own systems can react to issue, comment, cycle, and related changes.

Who can create which subscriptions

Scope Who can manage it
Workspace Workspace owners and admins
Project Project members (pick a project)

Open Settings > Webhooks.

1. Create a subscription

Choose Create webhook. The wizard has three steps.

Step 1 — Scope

Choose Workspace or Project. For project scope, select a project.

Step 2 — Endpoint

  1. Enter the URL Tixio should POST to.
  2. Optionally add a Description shown in Settings.
  3. Leave Enabled on unless you want to create a disabled subscription.

Step 3 — Event types

Either:

  • Choose Subscribe to all (*), or
  • Pick event types from the grouped list (Issues, Comments, Cycles, Labels, Projects, Epics).

Use Search event types to filter (for example issue. or comment.created).

Common issue events include issue.created, issue.updated, issue.deleted, issue.labels_changed, issue.cycle_changed, and issue.git_links_changed. Cycle events include cycle.started and cycle.closed.

Save the secret

After create, Tixio shows the Webhook secret once. Copy it, store it securely, then confirm I've saved this secret securely.

Verify incoming requests with the stored secret and the X-Tixio-Signature header. You will not see the full secret again unless you rotate it.

2. Monitor subscriptions

The webhooks list shows URL, events, last delivery, status, and an Enabled toggle.

Status badges:

  • OK — recent deliveries look healthy.
  • Failing — recent delivery failed, is retrying, or is dead-lettering.
  • Auto-disabled — Tixio stopped delivery after repeated failures.

Open Deliveries for a subscription, or use banners such as Webhook unhealthy / Webhook auto-disabled that link to the delivery log.

Actions on a row:

  • Deliveries — open the log.
  • Rotate — issue a new secret (shown once).
  • Delete — removes the subscription and its delivery log.

You can toggle Enabled after create. To change URL or event types, delete and recreate the subscription.

3. Use the delivery log

On Delivery log:

  1. Filter by Status (All, pending, succeeded, failed, dead_letter) and Event type.
  2. Inspect a row for time, attempts, duration, and HTTP status.
  3. Open the detail drawer for request body, headers, and attempt outcomes.
  4. Choose Replay when you need Tixio to send an event again.

The log refreshes while deliveries are pending so you can watch retries.

Good first subscriptions

  • A project-scoped subscription for issue.created and issue.updated into your chat or ops bot.
  • A workspace-scoped subscription for cycle start/close events into a reporting pipeline.
  • A narrow set of event types first — widen after your endpoint is stable.

Next