How to ensure booking webhooks return Google Meet URLs (not Cal Video/Daily) for API-created events?

[Nicollerl]

Hi team 👋

We create bookings via API and need the webhook payload to include the Google Meet URL as the primary meeting link instead of Cal Video/Daily or Office365 links.

Context

Organizer uses Google Workspace (e.g., torrevide@coninsa.co) connected to Google Calendar.

Event Type is virtual; we want Google Meet as the conferencing provider.

Current webhook shows:

location: "integrations:office365_video" (sometimes Cal Video)

videoCallData.type: "daily_video"

metadata.videoCallUrl points to https://app.cal.com/video/...

videoCallData.url points to https://*.daily.co/...

Example webhook (anonymized):

{
"triggerEvent": "BOOKING_CREATED",
"payload": {
"type": "virtual",
"location": "integrations:office365_video",
"videoCallData": {
"type": "daily_video",
"url": "https://example.daily.co/ROOM_ID"
},
"metadata": {
"videoCallUrl": "https://app.cal.com/video/BOOKING_UID"
}
}
}

What we want

Webhook to include the Google Meet URL as the primary link (ideally in metadata.videoCallUrl, or a dedicated Meet field).

Prevent Cal Video/Daily URLs from being generated when the event is configured for Google Meet.

What we’ve tried

Organizer’s Google Calendar connected; Google Workspace verified.

In Event Type → Location, selected Google Meet.

Disabled Cal Video/Daily app at the Event Type level (when possible).

In API bookings, attempted to enforce:

{
"location": "integrations:google_meet"
}

Despite this, the webhook sometimes still returns daily_video.

Questions

What’s the correct way to force Google Meet via API so the webhook returns a Meet URL?

Is location: "integrations:google_meet" sufficient?

Do we need extra fields (e.g., conferencingApp, conferenceData, etc.)?

Must we disable Cal Video/Daily at Event Type or organization level to prevent it from taking over?

In which webhook field should the final Google Meet link appear?

Should metadata.videoCallUrl already be the Meet link when the location is Google Meet?

Is there a priority order between the Event Type’s default location and the location we send via API?

Do you have an example request/response specifically for Google Meet?

Additional details

Time zone: America/Bogota

Flow: server-to-server booking creation → webhook BOOKING_CREATED

We can privately share complete request/response logs if needed (excluding tokens/JWT).

Thanks in advance! 🙏 Any guidance or a sample payload to reliably produce Meet links would be great.

[dosubot[bot]]

Hi @Nicollerl! I'm Dosu and I’m helping the cal.com team.

To ensure your API-created bookings use Google Meet and that the webhook returns the Meet URL as the primary link, set "location": "integrations:google_meet" in your API request. This field takes priority over the Event Type default location and organizer defaults. If the Google Meet integration is active and the organizer's Google Calendar is connected, the webhook payload will include the Google Meet link in metadata.videoCallUrl (source).

No extra fields like conferencingApp or conferenceData are required to force Google Meet, but if the integration is missing or fails, the system will fall back to Cal Video/Daily/Office365, depending on what's available. Disabling Cal Video/Daily at the Event Type or org level can help prevent fallback, but the API respects the explicit location field first.

The priority order is: API request location (if provided and non-empty) > Event Type default location > organizer's default conferencing app > fallback to Daily.

When successful, the webhook payload will look like:

{
  "triggerEvent": "BOOKING_CREATED",
  "payload": {
    "type": "virtual",
    "location": "integrations:google_meet",
    "metadata": {
      "videoCallUrl": "https://meet.google.com/abc-defg-hij"
    },
    // ...other fields
  }
}

If you still see Daily or Cal Video links, double-check the Google integration status and permissions for the organizer. If Google Meet can't be provisioned, fallback providers will be used automatically (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Nicollerl]

Hi @dosu — thanks! We switched our API payload to
location: "integrations:google_meet" and the webhook now shows that value, but it still falls back to Daily.

Webhook evidence (anonymized):

eventTypeId: 2091307

bookingId: 11113552

organizer: smontana@coninsa.co
(id 1436110)

payload.location: "integrations:google_meet" ✅

videoCallData.type: "daily_video" ❌

metadata.videoCallUrl: https://app.cal.com/video/1o9rJkT1ZxoAe3YmytT5cN (no Meet) ❌

We suspect missing Google scopes for creating conference links. We’ll disconnect/reconnect the organizer’s Google Calendar in Cal.com (accepting all scopes) and disable Cal Video/Daily at the Event Type level to avoid fallback.

Could you confirm if a specific Google scope/permission is required by Cal.com to provision Meet links? If there’s a diagnostic log we can check for “Meet provisioning failed,” that would help.

Thanks!

[dosubot[bot]]

To provision Google Meet links, Cal.com requires the organizer to grant the following Google OAuth scopes: https://www.googleapis.com/auth/calendar.events and https://www.googleapis.com/auth/calendar.readonly. These are checked during the Google Calendar integration process—if any are missing, Cal.com will not be able to create Meet links and will fall back to another provider like Daily.co. The OAuth flow also requests access_type "offline" and prompt "consent" to ensure refresh tokens are obtained for long-term access (source).

If Meet provisioning fails (for example, due to missing scopes, expired tokens, or revoked permissions), Cal.com logs errors with details in the server logs. Look for errors like BookingCreatingMeetingFailed or warnings about missing Google Calendar integration in your server logs (source). There is no single "Meet provisioning failed" message, but these logs will indicate what went wrong.

Troubleshooting checklist:

• Make sure the organizer reconnects their Google Calendar and accepts all requested permissions/scopes.
• Confirm that the Google Calendar integration is active and not expired or revoked.
• Disable fallback providers (Cal Video/Daily) at the Event Type or org level if you want to avoid fallback.
• Check server logs for errors or warnings related to Google Calendar or Meet provisioning.

When everything is set up correctly, the webhook payload will include the Google Meet URL in metadata.videoCallUrl. If you still see fallback to Daily, it's almost always a permissions or integration issue (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}