Connector Improvement: Webhooks Connector to sync delivery headers
Completed
For certain use cases where we use webhooks (e.g. Github), the delivery headers contain critical information, without which the data synced via the connectors is rendered useless. There should be an option to sync these delivery headers to the destination along with the payload for such cases.
-
Official comment
Hi Madhusudan, thanks for submitting this request! Can you give me an example of a critical header and the purpose it serves downstream?
Best,
Parmeet -
this is useful to understand github events as they dont make much sense now using webhooks
-
Hi Parmeet,
I would refer you to examples for Github/Gitlab, where headers contain critical info like X-Gitlab-Event / X-Github-Event which helps identify which type of event is synced.
You can refer to the documentation link for more headers that are synced, but most of them are essential in tracking successful deliveries, segregating datasets and avoiding duplicates downstream.
https://docs.github.com/en/webhooks/webhook-events-and-payloads#status -
Understood, thank you!
-
Hi Madhusudan, webhook delivery headers are now made available in the destination table. Details here: https://fivetran.com/docs/connectors/events/webhooks#schemainformation.
Thank you!
Parmeet
Please sign in to leave a comment.
Comments
5 comments