Integrations

Connect Qodex to source control, coding agents, webhooks, notifications, and your own LLM key 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, remote MCP access for coding agents, Slack webhooks, generic webhooks, email digests, and project-level OpenAI BYOK. Additional issue trackers, observability tools, and LLM providers are planned.

Available today

GitHub

Install the GitHub App, link repositories, run PR reviews, and sync generated tests.

GitLab

Link GitLab.com projects and review merge requests from Qodex.

MCP

Use Qodex projects, saved tests, and findings from a coding agent.

Slack webhook

Send scheduled run summaries to a Slack channel.

Generic webhook

POST run-completion JSON to your own endpoint.

Bring your own key

Use a project-owned OpenAI key for Qodex LLM calls.

Email digest

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 send generated test scripts back to code.
GitLab	Review merge requests and keep Qodex code context current for linked GitLab.com projects.
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 for a project’s Qodex usage.

Where to configure integrations

Open a Qodex project and go to Settings > Connections. The GitHub and GitLab guides include the provider-specific linking and removal flows. MCP keys live in Settings > MCP, and the OpenAI key lives 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 Settings panel may show planned connectors before they are wired end to end.

Planned area	Expected use
Bitbucket	PR review support outside GitHub and GitLab.
Linear, Jira, and GitHub Issues	Turn confirmed findings into tickets.
Microsoft Teams	Native team notifications.
Sentry, PostHog, and Datadog	Use production signals 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

GitHub

Connect repos and enable PR review.

GitLab

Connect GitLab.com projects for merge-request review.

MCP

Connect Qodex to a coding agent.

Slack

Send test-run summaries to a channel.

Generic webhook

Send run results to any HTTPS endpoint.

Run tests on a schedule

Configure notification timing and recipients.