Every deployed bridge gets a unique webhook URL that third-party services can call to trigger the bridge. This is useful for event-driven integrations where an external system needs to push data to your bridge.

After deploying a bridge, the webhook URL is shown in the deployment success message. You can also find it in the Settings tab of the bridge editor.

Webhook URLs include a unique token for authentication. The token is generated on first deploy and persists across redeployments. If you need to invalidate the webhook URL, you can regenerate the webhook token from the Settings tab — this creates a new URL and invalidates the old one.