What CodeLynq does with webhooks
Register an endpoint and CodeLynq POSTs to it when a development run completes or fails. Two events, deliberately — we would rather ship the ones that genuinely fire than advertise a catalogue where most entries never do.
Use it for whatever Slack does not cover: updating a ticket, writing to a dashboard, kicking off a job of your own, or feeding your own notification system.
Setting it up
- Add an endpoint in your organisation settings. The signing secret is shown once, at creation.
- Choose which events it receives, or leave the selection empty to receive all of them.
- Send a test delivery from the same screen and confirm it arrives.
- Verify the signature header on your side before trusting a payload.
Worth knowing
Each delivery carries an X-CodeLynq-Signature header — an HMAC-SHA256 over the exact bytes sent, with the body serialised canonically so you can verify against the raw request rather than re-encoding it. The event type and a delivery id travel alongside. Failures retry five times with exponential back-off, and every attempt — status code, duration, error — is kept in a delivery log you can inspect, so a broken endpoint is visible rather than silent. Payloads themselves are not stored.
Other integrations
CodeLynq also works with coding agents, GitHub, GitLab, Bitbucket, GitHub Actions, Fireflies, Plaud, Slack and MCP.