Configure webhooks

Connect Kera with external services using webhooks. Send events out when tickets change, and receive events from GitHub, GitLab, and other tools.

Outbound webhooks

Kera sends HTTP POST requests to external services when workflow transitions fire.

  1. 1 Add a webhook action to a transition

    In your workflow YAML, add a send_webhook action to any transition. Kera will POST to that URL every time the transition fires.

    transitions: - from: in_progress to: in_review actions: - type: send_webhook url: https://ci.example.com/trigger

  2. 2 Understand the payload

    Kera sends a JSON POST request with the full ticket context. The payload includes everything you need to act on the event.

    // Outbound webhook payload { "event": "transition", "ticket_id": "KER-42", "title": "Fix login timeout", "from_state": "in_progress", "to_state": "in_review", "actor": "max@example.com", "timestamp": "2026-04-24T10:30:00Z", "fields": { /* all ticket fields */ } }

  3. 3 Common use cases

    Trigger CI/CD pipelines when tickets move to review, notify a Slack channel when tickets are done, or sync state with an external tracker.

Inbound webhooks

External services send events to Kera to auto-link PRs, update ticket status, and sync pipeline results.

  1. 1 Set up an integration

    Go to your workspace settings and add an integration for GitHub or GitLab. Each integration creates a unique webhook URL.

  2. 2 Copy the webhook URL

    Each integration gets a unique endpoint:

    https://your-workspace.getkera.eu/webhooks/inbound/{slug}/{token}

  3. 3 Configure your source

    In GitHub or GitLab, add the webhook URL to your repository settings. Select the events you want to send (push, pull request, pipeline, etc.).

  4. 4 Automatic linking

    Once configured, Kera automatically links PRs to tickets by matching branch names and commit messages. It updates ticket status on merge and syncs pipeline results.

Tips

  • Inbound webhooks are verified via signature (GitHub) or token (GitLab) — unverified requests are rejected.
  • All webhook events appear in the workspace audit trail for full traceability.
  • Failed outbound webhooks are logged but not retried — design your receivers to be idempotent.
  • You can add multiple send_webhook actions to a single transition to notify several services at once.

Next steps