> ## Documentation Index > Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect Qodex to source control, observability tools, coding agents, webhooks, notifications, and your own LLM account so test results fit into your team's workflow. # Integrations Integrations connect Qodex to the places your team already reviews code, receives alerts, and manages test outcomes. Today, Qodex supports GitHub and GitLab source control; Bugsnag, Sentry, Datadog, Rollbar, and PagerDuty connectors; any custom MCP server; remote MCP access for coding agents; Slack webhooks; generic webhooks; email digests; and project-level OpenAI BYOK or your own ChatGPT subscription. Issue trackers and more LLM providers are planned. ## Available today > [card] [GitHub](https://qodex.ai/docs/integrations-github.md) > > Install the GitHub App, link repositories, and run PR reviews. > [card] [GitLab](https://qodex.ai/docs/integrations-gitlab.md) > > Link GitLab.com projects and review merge requests from Qodex. > [card] [Observability connectors](https://qodex.ai/docs/integrations-sentry) > > Connect Sentry, Bugsnag, Datadog, Rollbar, PagerDuty, or a custom MCP server. > [card] [MCP](https://qodex.ai/docs/integrations-mcp.md) > > Use Qodex projects, saved tests, and findings from a coding agent. > [card] [Slack webhook](https://qodex.ai/docs/integrations-slack.md) > > Send scheduled run summaries to a Slack channel. > [card] [Generic webhook](https://qodex.ai/docs/integrations-generic-webhook.md) > > POST run-completion JSON to your own endpoint. > [card] [Bring your own key](https://qodex.ai/docs/integrations-byok.md) > > Use a project-owned OpenAI key or your own ChatGPT subscription. > [card] [Email digest](https://qodex.ai/docs/run-tests-on-schedule.md) > > Email scheduled run results to project recipients. ## What each integration helps with | Integration | Use it when you want to | | - | - | | GitHub | Review pull requests, connect repos to projects, and give the agent your codebase. | | GitLab | Review merge requests and keep Qodex code context current for linked GitLab.com projects. | | Observability connectors | Pull production errors, events, and incidents on a schedule, reproduce them as tests, or use them on demand in chat. | | Custom MCP server | Give the agent the tools of any remote MCP server, such as internal tooling. | | MCP | Let a coding agent inspect Qodex projects, run saved tests, and triage findings over remote MCP. | | Slack webhook | Notify a team channel when scheduled tests pass or fail. | | Generic webhook | Route Qodex results into Teams, Discord, PagerDuty, internal tooling, or a relay service. | | Email digest | Send scheduled run summaries without requiring a chat tool. | | Bring your own key | Pay the LLM provider directly, or use your own ChatGPT subscription, for a project's Qodex usage. | ## Where to configure integrations Open the account menu at the bottom of the left navigation, choose **Settings**, then open **Connections**. The page lists what the project is connected to, then everything it can connect to, grouped as **Source control**, **Observability**, and **Custom**. The GitHub and GitLab guides include the provider-specific linking and removal flows. MCP keys live in **Settings > MCP**, and the OpenAI key and ChatGPT subscription live in **Settings > LLM keys**. Some integrations, such as schedule notifications, also appear in the workflow where they are used. For example, Slack and email notification fields live on schedule policies because the notification behavior is schedule-specific. ## Notification routing Qodex uses the same run-completion dispatcher for Slack and generic webhooks. * If the webhook host is `hooks.slack.com`, Qodex sends a Slack-formatted message. * If the URL is anything else, Qodex sends a generic JSON payload. * Email recipients are stored separately on the schedule. This lets you start with a Slack channel and later route the same run events into another system. ## Remove a configured integration For an integration with its own details page, open **Settings > Connections**, open that integration, click **Delete**, and confirm **Delete**. Qodex stops its schedule and destroys its saved credentials, while keeping past run chats. For source-control connections, use the GitHub or GitLab guide instead: unlinking a repository and disconnecting an account have different effects. ## Planned integrations The **Connections** page may show a planned connector, such as Bitbucket, before it can be connected. | Planned area | Expected use | | - | - | | Bitbucket | PR review support outside GitHub and GitLab. | | Linear, Jira, and GitHub Issues | Turn confirmed findings into tickets. | | Slack app, Microsoft Teams, and Discord | Native team notifications. | | PostHog | Use product usage to prioritize tests. | | Anthropic and Google BYOK | Use non-OpenAI provider keys for LLM calls. | Until those ship, use generic webhooks to connect Qodex to relay services or internal automation. ## Next steps > [card] [GitHub](https://qodex.ai/docs/integrations-github.md) > > Connect repos and enable PR review. > [card] [GitLab](https://qodex.ai/docs/integrations-gitlab.md) > > Connect GitLab.com projects for merge-request review. > [card] [MCP](https://qodex.ai/docs/integrations-mcp.md) > > Connect Qodex to a coding agent. > [card] [Slack](https://qodex.ai/docs/integrations-slack.md) > > Send test-run summaries to a channel. > [card] [Generic webhook](https://qodex.ai/docs/integrations-generic-webhook.md) > > Send run results to any HTTPS endpoint. > [card] [Run tests on a schedule](https://qodex.ai/docs/run-tests-on-schedule.md) > > Configure notification timing and recipients. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.