Gmail Connector
Send email as the signed-in user's own Gmail account via OAuth
- What
- Send email as the signed-in user's own Gmail account via OAuth
- Cost
- Free
- Needs
- a Caffeine AI project (backend Motoko canister); a Google Cloud project with an OAuth 2.0 Web-application client (client ID + secret, entered in the app's admin settings); the googlemail-client, google-oauth and caffeineai-authorization mops packages
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Gmail connector for Caffeine AI apps: the mandatory recipe for sending mail through the signed-in user's own Gmail account, built on the `googlemail-client` mops package (generated Gmail REST API bindings) plus `google-oauth` (token exchange, refresh, PKCE). Each end-user authorizes the canister independently via an OAuth 2.0 Authorization Code flow with PKCE; access and refresh tokens are stored per-user, and the 1-hour token is silently refreshed and retried on 401. Distinct from the `email*` extensions — those send transactional mail FROM the app; this connector acts AS the user's own Gmail. By @caffeinelabs, listed here with credit to its creator. Honest caveats: works only inside a Caffeine AI build; you must create a Google Cloud Web-application OAuth client, register the app's `/connect/gmail` callback URI as an authorized redirect, and enter the client ID/secret through the app's admin settings page (the secret stays in the canister, never the frontend); the skill explicitly forbids hand-rolled HTTP calls to Google endpoints — only the mops packages are the supported path. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Caffeine AI project (backend Motoko canister); a Google Cloud project with an OAuth 2.0 Web-application client (client ID + secret, entered in the app's admin settings); the googlemail-client, google-oauth and caffeineai-authorization mops packages Install "Gmail Connector" for me. Send email as the signed-in user's own Gmail account via OAuth Repository: https://github.com/caffeinelabs/skills/blob/main/skills/connector-googlemail/SKILL.md 1. Fetch the SKILL.md file for the caffeinelabs-connector-googlemail skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "caffeinelabs-connector-googlemail". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.