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
| Integration | What it does | Where |
|---|---|---|
| GitHub, GitLab, Bitbucket | The repositories CodeLynq works in and opens pull requests on | Project → Settings → Repositories. See Repositories. |
| CI webhook (GitHub) | Picks up failing checks and review comments, merges and workflow results | Per repository. See CI feedback loop. |
| Slack | Run notifications in a Slack channel | Settings → Integrations |
| Webhooks | Signed HTTP calls to your own systems when runs complete or fail | Settings → Integrations |
| Fireflies | Import meetings as meeting notes | Settings → Meeting sources. See Meeting notes. |
| Monitoring tools | Alerts become bug tasks | Project → Settings → Alerts. See Alerts. |
| GitHub Actions, deploy webhooks | Start your deployments | Project → Settings → Deployments. See Deployments. |
| AI assistants (MCP) | Let Claude or another assistant work with CodeLynq | See External AI assistants. |
| API | Your own scripts and tools | See API tokens. |
| Identity providers | Single sign-on and SCIM | Settings → Single sign-on. See Single sign-on and security. |
| Self-hosted runners | Runs on your own machines | Settings → Runners. See Self-hosted runners. |
Slack notifications
- In Slack, create an incoming webhook for the channel you want (App directory → Incoming Webhooks) and copy its URL.
- In CodeLynq, go to Settings → Integrations → Slack notifications.
- 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.
- Go to Settings → Integrations → Webhooks.
- Enter the Endpoint URL.
- Under Events, tick
run.completed,run.failed, or neither to receive every event. - Optionally add a Description, and click Add webhook.
- 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.