This is an easy-to-use script for integrating Google Apps Script (GAS), Google Calendar, and Slack for personal use. For more robust development, consider using Google's official library, Aside.
$ git clone git@github.com:ganchiku/gas-calendar-slack.gitTo get started, you'll need to set up clasp, which is the Google Apps Script command-line tool. You can find it here. After installing clasp, run the following commands:
$ clasp login --no-localhostThis will generate a file at $HOME/.clasprc.json. Please set the values in this file as GitHub Secrets.
Before using this script, you'll need to create a Slack app for Bots and grant the app permission to post Slack messages. Make sure to set the following scopes for your Slack app:
- chat:write
- chat:write.customize
- chat:write:public
Important: Do not commit any credentials to your repository. Treat them with care.
To deploy your Google Apps Script (GSA), store the credentials in GitHub Secrets. The following variables are referenced in GitHub Actions to deploy the GSA script:
| KEY | VALUE |
|---|---|
| ACCESS_TOKEN | XXXX |
| CLIENT_ID | XXXX |
| CLIENT_SECRET | XXXX |
| ID_TOKEN | XXXX |
| REFRESH_TOKEN | XXXX |
| SCRIPT_ID | XXXX |
For application use, store the credentials in GSA Property manually. While there may be better ways to manage credentials, this approach is simple and straightforward. Use the following Script Properties:
Script Properties
| Property | Value |
|---|---|
| CALENDAR_ID | XXXX |
| SLACK_CHANNEL_ID | XXXX |
| SLACK_TOKEN | xoxb-XXXXXX |
- You can call the Property Service within GSA, but consider who initiates the GSA script.
To automate your script, set up a trigger with the following configuration:
- Trigger Type: Time-driven
- Function to Run: main
- Deployment: Head
- Event Source: Time-driven
- Type of Time-based Trigger: Minutes Timer
- Minute Interval: Every minute
- You can also use
ScriptAppto create a trigger, but consider who will run the script. In some cases, you can run the script usingclasp runin a GitHub Action workflow.