Are there any thoughts on best practice on Notification Webhook URL if we want to have multiple notification destinations? Should this be handled in the UI or should this be handled by the user setup (aws lambda, azure automation/function)?

Thread sent successfully to Harvestr

This is a great idea, unfortunately multiple webhook notifications are not currently possible within Airbyte, however it might be possible to configure it elsewhere using a lambda or another service that can forward the notifications. For now, I've sent this suggestion to our Product team so they can keep it in mind for the roadmap. You are also welcome to submit a feature request in Github with details on what you'd like to see.

Yes I'm sending webhooks to a central location and forwarding them to the appropriate team location from there. Just seems like something that should be configurable in the UI on a connection.

Agreed, I think this feature would be widely used! Thanks for the feedback.

Feedback was linked to Notifications

Linked feedback:

Are there any thoughts on best practice on Notification Webhook URL if we want to have multiple notification destinations? Should this be handled in the UI or should this be handled by the user setup (aws lambda, azure automation/function)?