(bug) Self-hosted: webhook events MEETING_STARTED and MEETING_ENDED not being triggered

[dsaada42]

Issue Summary

I am facing an issue with webhook events MEETING_STARTED and MEETING_ENDED not getting triggered.

I am receiving BOOKING_CREATED and BOOKING_CANCELLED events correctly from the same webhook setup and PING test works fine.

I have seen previous issues closed about this topic, some stated that the MEETING_STARTED and MEETING_ENDED might not get sent if the creation time was too close to the meeting time. I tried to create meetings at various time intervals , of various duration, joining and leaving the meeting with all attendees/organizer at many different times (before, during, after) but nothing got produced.

To give you more insight about what I am doing: I am developing a NestJS application listening for incoming webhooks from my self hosted cal.com instance to transform them into RabbitMQ messages for my event-driven architecture. (works perfectly fine for BOOKING_CREATED and BOOKING_CANCELED) I am not receiving anything about MEETING_STARTED or MEETING_ENDED

Steps to Reproduce

On Self-Hosted Cal (docker image latest) Setup Google Calendar and Google Meet Create a webhook with MEETING_STARTED or MEETING_ENDED events Book a meeting Attend the meeting with both attendee and organizer (with google meet link)

Expected behavior

We should be able to receive webhook events MEETING_STARTED and MEETING_ENDED

Other information

No response

Screenshots

No response

Environment

• [ ] app.cal.com
• [X] Self-hosted Cal

Desktop (please complete the following information)

- OS:Linux Ubuntu 24.04 LTS
- Node: v18.19.1
- npm: 9.2.0
- Docker: Docker version 26.1.1, build 4cf5afa

[CarinaWolli]

For these triggers to work, you need to run a cron job for /api/cron/webhookTriggers. We run it every 5 minutes using GitHub Actions (cron-webhooks-triggers.yml)