Webhooks Configuration

Fine-tune how Ticket Mate receives and processes real-time updates from Jira and GitHub.

Overview

Webhooks are the "central nervous system" of Ticket Mate. They provide the real-time connectivity that keeps your dashboard and your Jira projects in sync. Proper configuration ensures that every PR merge and every status change is reflected instantly.

How it Works

  1. The Signal: An event occurs in Jira (e.g., ticket updated) or GitHub (e.g., PR created).
  2. The Delivery: The external service sends an HTTP POST request to your Ticket Mate webhook endpoint.
  3. The Processing: Ticket Mate validates the signature, parses the payload, and triggers any relevant automation rules.

Configuration Areas

1. Jira Webhooks

Manage the connection between Atlassian and Ticket Mate.

  • Endpoint URL: Your unique listener address (e.g., https://your-workspace.ticketmate.com/api/webhooks/jira).
  • Secret Token: A shared secret used to sign payloads and prevent unauthorized spoofing.
  • Event Selection: Choose precisely which Jira events (Issue Created, Updated, Commented) should trigger sync.

2. GitHub Webhooks

Configure how your code-level events are handled.

  • Repo Filtering: Enable webhooks for all repositories or select specific ones.
  • PR Linking Logic: Define the pattern for matching PRs to tickets (default: TM-[ID]).

3. Resilience Settings

  • Retry Policy: Configure how many times Ticket Mate should attempt to process a failed webhook before flagging an error.
  • Rate Limiting: Protect your instance from "webhook storms" during high-activity periods (e.g., bulk Jira migrations).

Troubleshooting Webhooks

  • Payload Inspection: Visit Admin → Reliability → Webhooks to see the raw data of the last 100 events.
  • Signature Errors: Ensure the secret token in Jira matches the one in your System Settings.
  • Missing Events: Verify that the "Webhook" status in Jira is set to "Enabled".

Best Practices

  • Minimize Events: Only subscribe to the events you actually use to reduce system load.
  • Secure Your Endpoint: Always use HTTPS and ensure your secret tokens are rotated annually.

Related Documentation

  • Reliability - Monitoring the health of your webhook listeners.
  • Automation - How webhooks trigger local rules.

Last Updated: February 11, 2026 10:55 PM EST