What CodeLynq does with Slack
When a development run finishes or fails, CodeLynq posts to the Slack channel you nominate: what the task was, what happened, and a link straight to the pull request.
It is deliberately quiet. Notifications fire on completion and failure, not on every step a run takes through its pipeline — a bot that announces each stage gets muted within a week, and then it is not telling you about the failures either.
Setting it up
- In Slack, create an incoming webhook for the channel you want the updates in.
- Paste the webhook URL into your organisation settings in CodeLynq.
- Start a run. The next completion or failure posts to that channel.
Worth knowing
This uses an incoming webhook rather than a full Slack app, so there is no OAuth flow, no workspace-wide install and no permissions to review. The trade-off is that it is one-way: you can read run outcomes in Slack, but you cannot approve a spec or start a run from there. If you want events elsewhere as well, the same outcomes are available as signed outbound webhooks.
Other integrations
CodeLynq also works with coding agents, GitHub, GitLab, Bitbucket, GitHub Actions, Fireflies, Plaud, MCP and webhooks.