Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generic Webhook destination #16976

Open
3 of 4 tasks
MarconLP opened this issue Aug 10, 2023 · 0 comments
Open
3 of 4 tasks

Generic Webhook destination #16976

MarconLP opened this issue Aug 10, 2023 · 0 comments
Assignees

Comments

@MarconLP
Copy link
Member

MarconLP commented Aug 10, 2023

We're looking into redesigning the webhook system. The current system has several limitations:

  • only a single webhook per team
  • confusing to configure
  • occasional delays

We will likely start working on this in Q4 2023.

Related issues:

These goals are being considered and we'd love to hear user feedback, as well as ideas for stretch goals or implementation.

If you like this idea, please leave a 👍 or ❤️ reaction on this post to vote for it -- your votes and feedback help us prioritize what to work on next!

Plan

  • delivery system improvements
    • exponential retries, something retrying shouldn't slow down others
      retries
    • observability: success rate
  • multiple webhooks support per project
    • with the ability to customise which events trigger the webhook, URL, method, auth headers, and customising the payload
This was referenced Oct 11, 2023
@tiina303 tiina303 changed the title Webhook system re-design mega-issue Generic Webhook destination Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

4 participants