Hi, thanks for the PR and for reaching out.

This looks like a simple yet beneficial solution, especially for Contributor Day tickets.
However, could you please open a ticket and fill in the necessary details? We need to document this and involve the relevant stakeholders in discussions to gather feedback and opinions.

Please use the following link to open the ticket: Open Ticket

Additionally, there is a relevant ticket we've been discussing recently: #1371 Ticket

It's possible that if this ticket is adopted, the webhook might no longer be necessary, as there would be no need to maintain a separate sheet for Contributor Day. However, if there are other scenarios where this webhook would still be useful, please add that information to the ticket above. You're also welcome to share your thoughts in the discussion on #1371. Thanks!

It's possible that if this ticket is adopted, the webhook might no longer be necessary, as there would be no need to maintain a separate sheet for Contributor Day. However, if there are other scenarios where this webhook would still be useful, please add that information to the ticket above. You're also welcome to share your thoughts in the discussion on #1371. Thanks!

Just while waiting for the relevant place for this - a webhook would be really helpful for those who have external mailing systems (e.g. Brevo for WCEU) as we would then automatically add people to a XYZ mailing list depending on their tag.

As @renintw has mentioned, it'd be great to open a ticket and to describe which problems this PR is trying to solve.

Thank you for posting it as soon as possible, @ivankristianto! Please share the link here when you post it, thanks! :)

Thanks @dorsvenabili and @renintw

Here is the ticket created: #1383

Some thoughts from WCAsia organizers:

The webhook solves concerns beyond the Contributor Day (CD) registrations.
It can be used as active and realtime data of the attendees!
Some WordCamps rely on external vendors for badge printing, so up-to-date data at the time of printing the badge is important!
It also addresses realtime stats of Food Preferences (if any); dietary concerns & a11y concerns.
In practice, many times the HR buys the tickets in bulk for the teammates; and closer to the event date, the data is changed, resulting in many overlaps or misses.
The webhook addresses all these in realtime.
In the current scenario, all ticket changes are logged at the individual ticket level!
With the webhook, the master list will always have realtime data, and the concern of individual ticket-level log monitoring will ease up.

— @vachan

I can see how the ticket on GitHub can help with Contributor day ticket in Camptix and it will definitely help. However, our technology team is thinking beyond the Camptix system and incorporate with 3rd party registration system or datasheet that helps organizers planning event.

— @yuliyang

Based on our experience when for 3rd party badge printing services. Ticket type could be: sponsor, attendees, speakers etc.
Usually sponsors will get certain number of tickets, and also will buy normal tickets for their employees.
Before the registration, they could swapping ticket type, for various reasons.
And since the 3rd party badge printing doesn't get the updated data, the participant can have different color of the badge. This is one of the cause of delay in badge printing, and could end with a lot of mental hit, especially in flagship WordCamp.

— @ivankristianto

Update: The progress is currently stuck on the legal side. There are legal concerns regarding sending user data to third parties. Additionally, it has never been clearly stated anywhere in the past how the ticket purchasers’ data would be used, so this will also need to be discussed.