Skip to Content

Integrations: GitHub, GitLab, Bitbucket, CI, Slack and MCP

Everything CodeLynq connects to: GitHub, GitLab, Bitbucket, CI, Slack, webhooks, meeting tools, monitoring, deployments and MCP, and where to set each up.

CodeLynq connects to the tools your team already uses. This page lists every integration and where to set it up. Most organization-wide integrations are set up by organization admins under Settings (in the sidebar, under Organization).

Overview

IntegrationWhat it doesWhere
GitHub, GitLab, BitbucketThe repositories CodeLynq works in and opens pull requests onProject → Settings → Repositories. See Repositories.
CI webhook (GitHub)Picks up failing checks and review comments, merges and workflow resultsPer repository. See CI feedback loop.
SlackRun notifications in a Slack channelSettings → Integrations
WebhooksSigned HTTP calls to your own systems when runs complete or failSettings → Integrations
FirefliesImport meetings as meeting notesSettings → Meeting sources. See Meeting notes.
Monitoring toolsAlerts become bug tasksProject → Settings → Alerts. See Alerts.
GitHub Actions, deploy webhooksStart your deploymentsProject → Settings → Deployments. See Deployments.
AI assistants (MCP)Let Claude or another assistant work with CodeLynqSee External AI assistants.
APIYour own scripts and toolsSee API tokens.
Identity providersSingle sign-on and SCIMSettings → Single sign-on. See Single sign-on and security.
Self-hosted runnersRuns on your own machinesSettings → Runners. See Self-hosted runners.

Slack notifications

  1. In Slack, create an incoming webhook for the channel you want (App directory → Incoming Webhooks) and copy its URL.
  2. In CodeLynq, go to Settings → Integrations → Slack notifications.
  3. Paste the Slack incoming webhook URL (it starts with https://hooks.slack.com/) and click Save webhook.

Run notifications are now posted to that channel. To change the channel, enter a new URL and click Update webhook; Remove webhook stops the notifications.

Webhooks

Webhooks send an HTTP POST to your own system when a run completes or fails.

  1. Go to Settings → Integrations → Webhooks.
  2. Enter the Endpoint URL.
  3. Under Events, tick run.completed, run.failed, or neither to receive every event.
  4. Optionally add a Description, and click Add webhook.
  5. Copy the signing secret that appears - it is shown only once - and click I have saved it.

Every delivery is signed with that secret in the header X-CodeLynq-Signature: sha256=…: an HMAC-SHA256 of the raw request body. Compute the same value on your side to check the request really came from CodeLynq.

For each webhook you can:

  • turn it off and on again with Active,
  • send a test event with Test,
  • see recent Deliveries: time, event, attempt, status and duration,
  • Delete it.

Organization standards

Not an integration, but set up in the same place: under Settings → Standards, admins add rules that every run in the organization follows - conventions, decisions, structure and known pitfalls. Write each rule so it makes sense on its own. The number of rules is limited, so keep them focused.

Test it on a task from your own backlog

Send us one real task. We run CodeLynq on your repository and you review the pull request. Free, within 5 working days of approving the spec.