Spike: Google Calendar Integration #163

Closed
opened 2024-09-15 19:28:53 +00:00 by PokeJofeJr4th · 3 comments
PokeJofeJr4th commented 2024-09-15 19:28:53 +00:00 (Migrated from github.com)

Template Instructions

Use this template to create a new Spike item.

Google Calendar Integration

Problem Statement

We want to add integrations between our website and Google Calendar.

Goal

We want to learn how to use a library or API to handle Google Calendar events.

Hypothesis

I expect there is a library or API we can use to integrate with google calendar. I expect we will be able to use this with nextauth.

# Template Instructions Use this template to create a new Spike item. # Google Calendar Integration ## Problem Statement We want to add integrations between our website and Google Calendar. ## Goal We want to learn how to use a library or API to handle Google Calendar events. ## Hypothesis I expect there is a library or API we can use to integrate with google calendar. I expect we will be able to use this with nextauth.
rtyocum commented 2024-09-22 17:59:26 +00:00 (Migrated from github.com)

Are we editing events on the website or just reading? Google calendar is easy for read access, requires oAuth, or a service account for the google calendar api to write to it

Are we editing events on the website or just reading? Google calendar is easy for read access, requires oAuth, or a service account for the google calendar api to write to it
2nPlusOne commented 2024-09-23 03:36:09 +00:00 (Migrated from github.com)

Are we editing events on the website or just reading? Google calendar is easy for read access, requires oAuth, or a service account for the google calendar api to write to it

Double check the vision document for the MVP requirements. The SSEs google account with our calendar has what we need, but we need to think about best practices for secrets management when using that.

> Are we editing events on the website or just reading? Google calendar is easy for read access, requires oAuth, or a service account for the google calendar api to write to it Double check the vision document for the MVP requirements. The SSEs google account with our calendar has what we need, but we need to think about best practices for secrets management when using that.
2nPlusOne commented 2024-09-23 03:37:38 +00:00 (Migrated from github.com)

I don’t have the link on hand right now but you can find it in the bookmarks for the technology channel in slack.

I don’t have the link on hand right now but you can find it in the bookmarks for the technology channel in slack.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SSE/WebsiteTheSSEquel#163
No description provided.