trouble adding Google Calendar to Cal.com App Store

[sparkwise]

I tried following the self-hosters instructions to add Google Calendar to the app, but have run into an issue (error message: "Google client_id missing") that I think might be specific to the Cloudron setup. Ultimately, it looks like we need to add these two new environment variables:

GOOGLE_API_CREDENTIALS={"web":{"client_id" ... }}
GOOGLE_LOGIN_ENABLED=true

and then re-seed the app store:

cd packages/prisma
yarn seed-app-store

I'm seeing lots of errors when running this that appear to be related to apps that I'm not trying to install, but I did see one error message that perhaps needs to be addressed here: error: Environment variable not found: DATABASE_URL.

I saw that the cal.com documentation mentions .env (here) and .env.appStore (here), so I tried putting the new variables there too (in addition to the current env file in Cloudron), but still no luck.

I'm curious to hear if anyone else has been able to successfully connect Google Calendar.

[3699n]

I was able to successfully set up the Google Calendar app by following the Cal.com self-hosters instructions you linked. I created it as an "Internal App". After including the GOOGLE_API_CREDENTIALS variable in the .env file I had to restart the Cal.com cloudron app twice for it to properly recognize the OAuth Credentials.

Please be aware that you need to enclose the JSON value of the environment variable in single quotes ' and apparently include a new line after your last environment variable.

It should look something like this:

# Add custom environment variables in this file

NEXT_PUBLIC_APP_NAME="..."
NEXT_PUBLIC_COMPANY_NAME="..."
GOOGLE_API_CREDENTIALS='{"web":{...}}'

# don't forget to include the new line after the env variable

Note it is not necessary to reseed the app store as described in Cal.com docs. Simply restart the Cloudron Cal.com app after adding the env varible and navigate to the admin settings to enable the Google Calendar app for your instance. You can also skip the admin onboarding dialog where you can enable the Google Calendar plugin.

[3699n]

After switching the Google OAuth Screen App from Internal to External with testing, adding my Google accounts to the list of testing users, I have been able to add all 3 of Google accounts across different orgs. Everything seems to be working well!

[nebulon]

Nice, thanks for sharing that. @sparkwise does it work for you then as well with this info?

[robertdoneill]

is there a copy of the .env file created in the home directory? When i look at mine I only see .env.example but no .env file. It seems like it should be there someplace that Im missing.

[girish]

@robertdoneill Use the filemanager to edit /app/data/env

[sparkwise]

@nebulon I wasn't able to get it to work with changes to the env file, but was able to get everything working through a different path: by first uninstalling and reinstalling from the Cloudron App Store. This time, I entered the credentials directly through the web prompts during the admin user onboarding flow. Looking forward to testing it all out this week!

[jessencan]

Thanks for posting about this! I also tried to connect Google Calendar to the Cal.com app on my Cloudron instance and ran into issues.

The error about the missing DATABASE_URL environment variable stood out to me as well. My guess is that the seed-app-store command expects certain env vars to be defined globally, while we've only set them in the cal.com service specifically.

Perhaps we need to temporarily define DATABASE_URL (and any other required vars like SECRET_KEY_BASE) in the global Cloudron .env file before running the command. Then we can remove them after.

I haven't tested this theory out yet but plan to. If you or anyone else finds a working solution for adding Google Calendar integration please do share! Getting Cal.com linked with Google Calendar would be huge for my use case.

Also, if the developers are open to it, it could help to have some Cloudron-specific instructions for getting the integration working. The self-hosting steps don't quite translate over cleanly. But I'm sure they have a lot on their plates!

[3699n]

@jessencan I never reseeded the app store after adding the GOOGLE_API_CREDENTIALS to env file. It's not necessary. Simply restart the App and sign in with your admin account. Then you can enable the Google Calendar integration in the admin settings.

[jessencan]

thanks 3699n Solved.

The calendar for 2024 allows us to chart the passage of time during the upcoming year. Its structured grid of days, weeks and months provides a systematic framework to plan, organize and record important events or milestones. Unlike its digital counterparts, a physical 2024 calendar can hang on the wall as a constant reference. It gives a comprehensive snapshot of the year from January to December, where the date boxes act as placeholders for appointments, reminders and personal notations. The 2024 calendar accommodates the extra 24 hours by making February 29 days during the leap year. Whether designed for home or office use, calendars keep us grounded by mapping the year ahead while allowing space to document our memories.