The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
|Content Last Reviewed
Thanks for visiting this category direction page on Webhooks in GitLab. This page belongs to the Import and Integrate group of the Manage stage and is maintained by the group's Product Manager, Magdalena Frankiewicz (E-mail, Calendly).
This direction page is a work in progress, and everyone can contribute:
Webhooks are a generic way for projects to be integrated with any other service. GitLab's APIs allow other services to reach in to our data, Webhooks proactively send data to another service when certain events happen. These are increasingly important for external vendors, as they offer a key way to integrate with GitLab that doesn't require them building inside our codebase. Webhooks also give users, customers, and partners a more efficient pattern for receiving data triggered based on events, rather than inefficiently polling to see if any new events are available.
We want to increase the robustness of our webhook offering and align with other teams on how best to achieve an event-driven architecture. This includes making it easier to configure and maintain webhooks, as well as troubleshooting issues, easily redelivering events, and coordinating webhooks into usable workflows.
Our customers should enjoy learning about and using our webhooks to design creative solutions and intelligent workflows, and be motivated to share GitLab as an example of an incredible third-party developer experience.
As we establish core webhook functionality, we'll want to collaborate with product teams within CI, AppDev, and Security areas to define generic patterns that enable scalable integration that satisfies our customer demand.
Please be aware that Webhooks is Viable maturity and we are putting this category in maintenance mode from FY24Q2 (May 2023). Due to this, there will be no dedicated investment in this category maturity until further notice. We will support only the most critical and severe bug fixes with significant business impact while we shift our attention to improve high-priority importers, GitLab to GitLab importer, GitHub importer and BitBucket Server importer.
When we resume regular work on this category, we plan to focus on:
See our planning epic.