Webhooks used to live in Settings → Webhooks, which is not where anyone looks for them. They're now a first-party connector in the Integrations marketplace, alongside Shopify and everything else that pushes data out of Lynkist.

Nothing about your endpoints changed — the same URLs, the same secrets, the same events. Your existing endpoints were moved across for you, and if you'd never created one, nothing was turned on.

What's better

Delivery history now paginates. Previously you saw a recent slice and no way to go further back.
Nine campaign events and flow.submission_received are now subscribable. They were fired by the backend but missing from the subscription list in the UI, so there was no way to actually receive them. We've added an automated check so the list can't silently drift from reality again.
Disconnecting is now a real action — it deactivates your endpoints and stops deliveries, rather than leaving them running invisibly.

Two corrections worth flagging

Who can manage integrations. Connecting and disconnecting integrations now requires the integrations-manage permission. Previously any signed-in team member — including agents — could connect or disconnect them.

Webhook secrets. The UI used to say your signing secret was stored only as a hash. That was wrong, and we've corrected the wording. Secrets are stored so we can sign each delivery, which means we can display them back to you. Encrypting them at rest is a change we still owe you, and it's on the roadmap.

If you build against the API, the endpoint paths for developers are unchanged — see the API changelog for anything contract-level.