Forwarded external webhooks not wrapped in Nango metadata

[amackera]

According to the documentation Receive webhooks from an API, forwarded webhooks should have the following format:

{
   "from": "hubspot",
   "type": "forward",
   "connectionId": "<CONNECTION-ID>",
   "providerConfigKey": "<INTEGRATION-ID>",
   "payload": ... // Raw payload from webhook
}

However, from my testing, the payload is not wrapped in any of the Nango metadata, and in fact only contains the payload from the external API. This makes it difficult (impossible?) to link the forwarded webhook with a connection in Nango.

[linear]

NAN-2475 Forwarded external webhooks not wrapped in Nango metadata

[TBonnin]

Nango simply forwards the webhook payload if it cannot link it to a connection. Does the connection exist in Nango?

[amackera]

Nango simply forwards the webhook payload if it cannot link it to a connection.

@TBonnin I guess this is a bug in the docs that mention the forwarded webhook would be wrapped with some metadata.

Does the connection exist in Nango?

Yes, the connection exists. It's a Salesforce connection. I created the webhook myself, so it makes sense that Nango would have trouble wrapping it in metadata.

Edit: It's not really a bug in the docs, but that additional info that Nango just forwards the webhook if it can't look up a connection would be valuable to have in the docs!

Also, I'm wondering, is there a "sanctioned" way to set up webhooks with Nango such that it can look up the connection? Would that be part of the Scale plan as indicated on the website?

Thanks for any insight @TBonnin

[TBonnin]

You are right that the documentation doesn't make any mention of the behavior when a connection can not be associated to a incoming webhook. Thank you very much for your feedback. We'll continue to improve our documentation.

Also, I'm wondering, is there a "sanctioned" way to set up webhooks with Nango such that it can look up the connection? Would that be part of the Scale plan as indicated on the website?

Nango is aware of the webhook format for the supported 3rd-party providers. Any webhook payload that doesn't match the expected format won't be matched to any connection and will be simply forwarded

[amackera]

Thanks @TBonnin for the help and the information!

So for instance in the Nango Salesforce documentation, it has a checkmark next to "Real time webhooks from 3rd party API". Is there a way to get Nango to create the webhook in Salesforce automatically, such that the forwarded webhook is wrapped with connection metadata?

Is that something that's only provided for paying users?