Group Meeting Question

Hello,

When creating a group meeting scheduler, is it possible to have it not show on the users google calendar until at least one participant (that isn’t the host) books a slot on an appointment?

Right now, once the scheduler is created, it’s creating all of the potential meetings on the associated calendar, even before anyone has signed up for it.

Thank you!

Bump. Any help please?

@marketmuscles - will clarify this with the team, and circle back.

Any luck, ram? Thank you!

@marketmuscles can you explain the use case further? Like what are you trying to achieve?

An alternative would be to consider collective meeting or a round robin scheduling.

Sure. I run a martial arts school and I allow 5 new students to try a class at a time.

I created a scheduler with the group meeting setting to allow multiple students to be able to schedule for the same time slot.

When I created the scheduler, it created meetings on my google calendar for every single time slot, even before anyone has booked an appointment.

My expectation would be that the appointment would not show up on my calendar until at least one person has secured a spot for the appointment.

Thank you.

@marketmuscles just to clarify was the scheduler created via Nylas API or using https://scheduler.nylas.com/?

It was made through the nylas api

Can you share code samples or API calls that I can review with the team and/or try out?

This is the guide that was followed: Set up group meetings | Docs

Normal schedulers are working fine, the issue is schedulers with type group where availability can be specified by creating group events

In other words, is there a way to hide created group events on my calendar until at least one person books? Or another option would be, a way to show availabilities on group schedulers without creating group events and only creating the group event once someone books.

Short answer - this is the standard flow: group events are pre-created with capacity, and people book into existing time slots vs. creating new events

Here are some possible workarounds / changes to help:

  • consider using the visibility: "private" config
  • shifting the scheduler to a virtual calendar, and only creating an event in your calendar after someone books in the virtual calendar