We are looking to migrate our calendar add-on to a self hosted runtime because we are running into limitations with apps script that we can not lift.
We follow this pattern: https://developers.google.com/workspace/add-ons/calendar/conferencing/sync-calendar-changes
Is there a way to do this with other runtimes other than Apps Script? It looks like installable triggers can not be HTTPS endpoints.
Push notifications also are not user authenticated and give no access to user storage like in apps script.
youโre right โ installable triggers like in apps script donโt work outside that environment. they canโt point to https endpoints and arenโt available in other runtimes
if you move to a self-hosted runtime, youโll need to use the calendar api with push notifications (watch). but these notifications arenโt user-authenticated and wonโt give you access to per-user storage unless you manage oauth tokens separately
your options are:
use oauth2 for each user, store tokens, and use the calendar api to sync changes
or keep a minimal apps script that handles triggers and forwards event data to your backend
the second option is easier short term if you want to avoid rebuilding the full auth and sync logic