Skip to content

Integrations

Configure integrations in the dashboard using the credentials and identifiers required by each connector. Use the connection test where available. Grant only the permissions needed and keep integration credentials out of browser code.

Integration Purpose and setup
GitHub Create issues in a configured repository. Repository selection requires issue support and push permission; installing an inbound issue webhook requires repository administration permission.
Jira Create issues and comments in Jira Cloud or a configured allowlisted Jira host. Configure the site and project and test access.
Linear Configure an API key and a team UUID, not the short team key. Available creation modes include manual, new issues and critical issues.
Sentry Resolve captured event IDs to Sentry issues. Test organization access and grant the read scopes needed by your Sentry installation.
Datadog Send issue lifecycle logs and use trace IDs for searches. Configure the site, API key and optional service.
Splunk Send events to HTTP Event Collector. Configure its HTTPS URL and token, with optional index and search settings. The deployment validates the destination against supported URL rules.
PagerDuty Configure an Events API v2 routing key for critical issues and regressions. Resolving an issue can resolve its corresponding incident.
Webhooks Deliver selected issue events to a public HTTPS endpoint. Verify the signature before processing a delivery.
MCP Connect a compatible coding agent using an mcp:read scoped key. Write operations also require server-side write enablement and mcp:write; fix drafts require human approval.

Supported events and synchronization differ by connector; creating a ticket does not imply that every later change is synchronized.

The default webhook subscriptions are issue.created, issue.regressed and issue.critical. Deliveries include X-BugFence-Event, X-BugFence-Delivery and X-BugFence-Timestamp. Verify X-BugFence-Signature-256 against the HMAC-SHA256 of the timestamp, a period, and the raw request body using your configured signing secret. Validate the timestamp and use the delivery ID to deduplicate retries.

Review the data and access required by each integration before enabling it. For application hosting and secret handling, see self-hosting security.