​

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

​

What each integration helps with

​

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. Until those ship, use generic webhooks to connect Qodex to relay services or internal automation.

​

Next steps