This article is specifically designed for the "server to server" authentication scenario. This means that your express server communicates with the Google API with authorization that has been setup ahead of time.
The scenario that you are describing is where a user gives certain authorizations to your app in order to do things such as add events to the users calendar. This would be where the user would see the " wants to add events to your calendar" and the user would say yes. At this point your app would receive a token to use in order to authenticate with the google API for that user.
While it is outside the scope of a comment to explain this in more detail, I hope this at least gets you on the right track.
I'm also very interested in this scenario. Some apps will have just have a one-time connect with google calendar (OAuth + consent) and from there on, any events created in that app will show up on my calendar, or on any users google calendars within that app.
I don't see how this could be automated as if you imported a webcal URL into google. I assume each time your application created an event it needs to push that event to all your users calendars (who already autorized your app) or, there is just one syncing server (Google CalDAV?) that your application can push events to, and that server knows how to update client calendars?
This is specifically designed to integrate an "administrated calendar" into a website. So this doesn't display user data, it displays data from a calendar that is administered behind the scenes and then displayed on a website.
This article is specifically designed for the "server to server" authentication scenario. This means that your express server communicates with the Google API with authorization that has been setup ahead of time.
The scenario that you are describing is where a user gives certain authorizations to your app in order to do things such as add events to the users calendar. This would be where the user would see the " wants to add events to your calendar" and the user would say yes. At this point your app would receive a token to use in order to authenticate with the google API for that user.
While it is outside the scope of a comment to explain this in more detail, I hope this at least gets you on the right track.
Can we make other people as an organizer of the meeting?
I'm also very interested in this scenario. Some apps will have just have a one-time connect with google calendar (OAuth + consent) and from there on, any events created in that app will show up on my calendar, or on any users google calendars within that app.
I don't see how this could be automated as if you imported a webcal URL into google. I assume each time your application created an event it needs to push that event to all your users calendars (who already autorized your app) or, there is just one syncing server (Google CalDAV?) that your application can push events to, and that server knows how to update client calendars?
This is specifically designed to integrate an "administrated calendar" into a website. So this doesn't display user data, it displays data from a calendar that is administered behind the scenes and then displayed on a website.
Thanks!