Notion → Google Calendar ← ICal

Sync from Notion databases and ICal feeds to Google Calendar

Configuration

See config/example.config.yaml for all available configuration options.

1. Obtain the necessary API tokens from Notion and Google
2. Configure each Notion database and how its properties map to Google Calendar events in config/config.yaml.
3. Configure each ICal feed in config/config.yaml.

Google API

Google OAuth 2.0 requires you to designate your project as either "Testing" or "Published." OAuth 2.0 tokens issued for "Testing" projects are only valid for one week, after which the user must complete the OAuth consent process again. Hence, using the credentials of the user will not work for automation. Instead, a service account can be used with the user's calendars shared with the service account.

1. Create a Service Account. Project permissions or IAM roles are irrelevant.
2. Generate a key for the service account (type JSON) and store it in secrets/google.json
3. In your Google Calendar UI, share every relevant calendar with the email of the service account, permission should be "Make changes to events".

Notion API

1. Create an integration for every workspace you want to sync from.

   • Integration type: "Internal integration"

2. Store the integration tokens in secrets/notion.json:

   {
   	"integration_tokens": {
   		"<workspace_name>": "<integration_token>"
   	}
   }

3. Add the integration to each database in Notion.

ICal

Because subscribing to an ical feed like an outlook calendar from google calendar sucks, with very slow syncing times, you can include an ical link in this syncing tool.

Recurring events are supported, apart from detecting deleted recurring instances on the side of Google Calendar. Make sure to create a new calendar in google for the ical feed and to not edit the events manually.

Scheduling & Monitoring

• Scheduling using Cron in a Docker container:
  Deploy as a docker container using docker-compose.yml and set the schedule using CRON_SCHEDULE in .env.

  docker compose up -d

  OR

  Run the docker container manually, also available on Docker Hub

• Monitoring using logfile:
  See logfile at logs/logfile

• Monitoring using Uptime Kuma:
  Set the correct push url using KUMA_PUSH_URL in .env.
  If Uptime Kuma is also running inside a container, user the container name and port instead of the external url: http://<kuma_container_name>:3001/api/...
  Make sure the cron schedule and hearthbeat interval in uptime kuma match.
  Make sure to add the running container to a shared docker network with the Uptime Kuma container.