Connecting Google and GitHub, and what each can and cannot do
One-click sign-in on Plus, your own free sign-in app on any plan, calendar read-only, Gmail through your own app, and what GitHub access covers.
Updated 4 Oct 2026
Open Apps to connect the services your agents may use. Sign-ins stay encrypted on this computer, and the AI never sees your passwords. Data goes from the service to your computer, not through Pivra.
Two ways to connect
| Pivra Desk's own sign-in | Your own sign-in app | |
|---|---|---|
| Plan | Comes with Plus | Free on every plan |
| Effort | One click (Google), or a short code (GitHub) | A one-time setup: about 10 minutes for Google, 5 for GitHub |
| Google scope | Calendar, read only, and your account email | Whatever you grant your own app, including Gmail |
If you connected with Pivra Desk's own sign-in and your plan lapses, the connection is kept and works again when you upgrade, or you can connect with your own app instead.
With Plus: press Connect next to Google. Pivra Desk's built-in sign-in asks Google for your calendar (read only) and your account email, nothing else. Your agent can then read your calendar; plain calendar questions ("what is on today?") are answered without a model at all, and calendar events never wake the agent on their own.
Pivra's Google sign-in app is still going through Google's verification, so the consent screen may warn that the app is unverified. The scopes it asks for are the two above.
Gmail needs your own Google sign-in app for now, on any plan:
- Under Google in Apps, open the steps for your own sign-in app. They take you to the Google Cloud credentials page.
- Create a project, turn on the Google Calendar API (and Gmail if you want mail), and create an OAuth client for a desktop app.
- Google then shows a Client ID and a Client secret. Paste both into Pivra Desk and save.
- Press Connect and sign in with Google.
With your own app your agent reads mail and your calendar, and sends mail only after your OK on an approval card. Without a connected mailbox, approved emails are saved as drafts for you to send.
Disconnect deletes the tokens on your computer and asks Google to revoke access.
GitHub
With Plus: press Connect next to GitHub. It signs in with GitHub's device flow: Pivra Desk shows a short code, you enter it on GitHub, and no secret ships in the app. Your agent can then see notifications, issues and pull requests, and changes wait for your OK. Tick Include private repositories if you want more than public ones.
On any plan: create your own GitHub sign-in app (about 5 minutes; Apps shows the steps), paste its details, and connect.
The Content & SEO template can open a drafted post as a pull request in a repo you name; it never merges.
What else connects
- MCP servers, local or remote, under Other tools → Add a tool. Remote servers sign in with OAuth; write tools sit behind approval like any other.
- Slack and Microsoft Teams, as your own bot, under Settings → Channels. Slack takes about 10 minutes and needs no public address. Teams needs a public address for now; the Pivra relay that removes that need is built but not switched on.
- Saved passwords, stored encrypted on this computer. Your agent only ever sees the name you give each one.
There is no Linear integration, and no app store of one-click integrations beyond the above.
Related
Was this helpful?
If you have questions or suggestions, email us at support@pivra.ai .