DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to manage Gmail, Calendar, and Contacts by text with Open Instinct

Connect a Google account so the assistant can work with your email, events, and contacts.

  • Life admin
  • Advanced
  • 120 minutes
  • From the README
  • Any agent

Credentials. The Google client-secret download holds OAuth credentials, so keep it outside the repository and never commit it.

Who it is forA professional who wants to ask an assistant to send email, schedule events, or look up a contact from iMessage.

The problemSwitching between Gmail, Calendar, and Contacts for simple requests takes time, and an assistant needs safe, user-scoped access to do it.

The outcomeA user-scoped Google grant lets the assistant read and modify Gmail, manage Calendar, and search read-only Contacts.

What you need first

  • A Vercel account on the Pro plan, since the Hobby plan cannot run the every-minute schedule
  • A Kernel account on its free plan for cloud browsers
  • A Neon account on its free plan for Postgres
  • An iMessage-capable phone to verify the managed Linq line
  • A Stripe account only if you want Link wallet purchases

Steps

  1. In Google Cloud, configure the OAuth consent screen and enable the Gmail API, Google Calendar API, and People API.
  2. Create OAuth web credentials, add https://connect.vercel.com/callback as a redirect URI, and download the client-secret JSON.
  3. Run jq '{clientId: .web.client_id, clientSecret: .web.client_secret}' /absolute/path/to/downloaded-client-secret.json > "$google_credentials_file" to make the file Vercel expects, then create the connector with vercel connect create google --connection-method oauth --name open-instinct --data @"$google_credentials_file".
  4. Run vercel connect attach --project <project> --environment production --yes and then rm -f "$google_credentials_file". (inferred, check the README)
  5. Set GOOGLE_CONNECTOR_UID to the returned UID and redeploy.

Prompt for your agent

Using the repo Merit-Systems/OpenInstinct, create and attach a Google connector for the project <project> and set GOOGLE_CONNECTOR_UID. Expected output: the connector UID and a redeployed app. Verify that the credential file was deleted and that no credential file is staged in git.

Caveat. A Google OAuth app in Testing mode only works for listed test users and those grants expire after seven days.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page