Would it be possible to integrate Google Meet with the Appointments system? Specifically, can we create an auto-generated Google Meet link in the booked appointment section? Alternatively, could we allow the instructor to configure which platform they want to use?
I've noticed comments and support requests about this feature in the past, and I'm wondering if any progress has been made on this.
Google meet currently does not have any api, the only way to connect it is via events. The issue was with recursive events so we did not create integration
I see. Actually, if you already have integrated the Google Calendar API with sync options, enabling recurring appointments is totally feasible. Maybe you're quite close!
About recursive events, to be honest, I don't rely much on recurring appointments. Because they require users to pay for all appointments at once, it makes it very difficult for patients to commit. It's different when paying per session or every four sessions, as this is more common.
We reviewed the google meet api and this again requires auth , the user has to login to his google account, its not a server to server app which will allow us to create meeting from the server end in background when appointment is booked so hence again architecture limitation from google .
Alex. This issue is over when authentication is fixed. I think Google Meet is great and shouldn't be left aside, because its adoption and market are huge! Adoption, meaning that people know how to used it. Yes, Jitsi.
so we had quite a discussion on this but did not end up in any conclusion. I have started work on this for a feasibility study i need couple of days to confirm this.
Would it be possible to integrate Google Meet with the Appointments system? Specifically, can we create an auto-generated Google Meet link in the booked appointment section? Alternatively, could we allow the instructor to configure which platform they want to use?
I've noticed comments and support requests about this feature in the past, and I'm wondering if any progress has been made on this.
Thank you!
Google meet currently does not have any api, the only way to connect it is via events. The issue was with recursive events so we did not create integration
I see. Actually, if you already have integrated the Google Calendar API with sync options, enabling recurring appointments is totally feasible. Maybe you're quite close!
check here. https://developers.google.com/calendar/api/guides/recurringevents
About recursive events, to be honest, I don't rely much on recurring appointments. Because they require users to pay for all appointments at once, it makes it very difficult for patients to commit. It's different when paying per session or every four sessions, as this is more common.
well i think you did not understand the main reason why we do not have this integration .
the issue is that google does not provide any way to create events from server backend .
in zoom we are creating meeting on the go as soon as appointment is booked .
you can create a booking and check zoom menu item that meeting is created .
the same cannot be done with google meet due to its own api limitation as of now.
That's not quite accurate. Google does have APIs that let you create events from a server backend.
I stand corrected, yet the api for Google meet are now live in feb'2024
https://workspaceupdates.googleblog.com/2024/02/google-meet-api-now-generally-available.html
this is great news, we can begin work on this.
We reviewed the google meet api and this again requires auth , the user has to login to his google account, its not a server to server app which will allow us to create meeting from the server end in background when appointment is booked so hence again architecture limitation from google .
its a disappointment again .
we can work on jitsi then.
Alex. This issue is over when authentication is fixed. I think Google Meet is great and shouldn't be left aside, because its adoption and market are huge! Adoption, meaning that people know how to used it. Yes, Jitsi.
so we had quite a discussion on this but did not end up in any conclusion. I have started work on this for a feasibility study i need couple of days to confirm this.