# Forwarded external webhooks arrive without Nango connection metadata

## What was going on

External webhooks forwarded through Nango arrive as just the raw third-party payload, with none of the documented Nango metadata like connectionId or integration id. That makes it impossible to link the webhook back to the connection it belongs to.

## The fix that worked

The recommended pattern: implement a custom script that creates the webhook in the third-party service, like Salesforce, when a connection is created, triggered by Nango's post-connection-creation event, and clean it up with the pre-connection-deletion event. That way you control the webhook registration and can attach the connection id yourself. The reporter confirmed this works.

## Where this came from

https://github.com/NangoHQ/nango/issues/3264