Connect GitHub to Gmail
Ideas
What you can do with GitHub and Gmail
Draft your weekly timesheet from email and commits
Every Friday you get an email with a draft timesheet, grouped by client and task, built from the emails you sent and the code you committed that week.
See how it worksOpen GitHub issues from failed backup emails
When a backup or scheduled job emails a failure report, a GitHub issue is opened with the details and you get an email with the link.
See how it worksMonitor your site and update a GitHub status page
If your site goes down you get an email within five minutes, and the status page you host on GitHub updates itself, then again when the site is back.
See how it worksEmail a weekly changelog from merged pull requests
Every Friday you get a customer-friendly changelog written from the week's merged pull requests, with any risky changes flagged for a second look.
See how it worksLabel new GitHub issues and email me about bugs
New GitHub issues are labelled by type automatically, and you get an email whenever one is a bug.
See how it works Your own logicAny other automation you can describe in words
Your own rules, schedule and AI steps with GitHub and Gmail, plus any other app. Describe it and your assistant builds it.
See how to build your ownBuild your own
Build any GitHub and Gmail automation you can describe
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
For example, ask your assistant
Every Friday, email me a summary of pull requests merged this week in our three repos, grouped by author, with AI-written one-line descriptions.
When an email with "bug" in the subject arrives, have AI decide if it is a real bug report; if so, open a GitHub issue unless one with a similar title is already open.
Use cases
Why people connect GitHub and Gmail
How the two apps work together
- GitHub sends events such as new issues, pull requests and releases to a ClickRuntime trigger link through its webhooks.
- The script formats the event and sends an email from your Gmail account, or files a GitHub issue from an email it finds.
- For the email side, the automation checks Gmail for new messages matching a label or search every few minutes.
Release notes emailed to customers
Product managers send a short email to a customer list when a GitHub release is published. The email lists merged pull requests by label, such as feature and fix, in plain language.
Customer bug reports become GitHub issues
Small engineering teams that take bug reports by email turn them into GitHub issues with the sender, subject and steps in the issue body. The reporter gets a reply with the issue link once it is filed.
Review reminders for stale pull requests
Engineering leads email each reviewer a list of pull requests waiting on them for more than two days. The email links each PR and shows its age and size.
Security advisory alerts by email
Maintainers get an email when Dependabot opens a security alert on a repository. The email names the package, severity and affected repository so it can be fixed the same day.
More apps
GitHub, Gmail and other apps in one automation
Release email to customers and a Slack post
When a GitHub release is published in our main repo, email the release notes to the list in my Gmail drafts and post a short version in #product.
Log emailed bug reports in a sheet and GitHub
When an email arrives with the label bug-report, open a GitHub issue and add a row to my Bugs sheet with the sender, subject and issue link.
Sentry errors to GitHub issues with email summary
Create a GitHub issue for each new Sentry error in production and email me a daily summary of the issues opened.
Setup
Connect GitHub and Gmail once
GitHub
Developer / Source control
- In GitHub, open your profile picture, then Settings, Developer settings, Personal access tokens, Fine-grained tokens, and choose Generate new token.
- Give it a name and an expiration, and choose the resource owner (you or your organization).
- Under repository access, pick only the repos the automation needs, then set the minimum permissions, such as Issues, Pull requests or Contents.
- Generate the token and copy it.
- In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for GitHub.
Gmail
- At console.cloud.google.com, create a project and enable the Gmail API under APIs & Services → Library.
- Set up the OAuth consent screen. On Google Workspace choose Internal. On a personal Gmail account choose External, then under Audience click Publish app so it is In production, not Testing.
- Under Data Access, add the scopes you need, such as
https://www.googleapis.com/auth/gmail.modify, orgmail.sendif you only want to send. - Under Clients, create an OAuth client of type Web application with the redirect URI
https://clickruntime.com/oauth/callback. - In the ClickRuntime dashboard, open Connections, choose Gmail and enter the client ID and secret. On a personal account Google shows an unverified-app screen: click Advanced, then go to your app.
FAQ
Questions about connecting GitHub and Gmail
Which inbox do the emails go to?
Can it send a changelog to customers?
Does it need access to my whole GitHub account?
Will my code be sent to AI?
Can it react to GitHub events right away?
Can I limit it to certain repositories or labels?
Does it work with GitHub organizations?
Related pages
Keep exploring
Tell your assistant what GitHub and Gmail should do together
Free plan. No credit card.