Google and Gmail sending
Google is a connector, not your sign-in. Connecting it never replaces your Pythe session, and the connected account can differ from the one you sign in with.
Updated 2026-10-13
Connecting Gmail used to go through the sign-in provider, which replaced your session: connecting an outreach inbox signed you out and back in as that account. Now it is a separate flow. google-oauth-start returns Google’s consent link, google-oauth-callback saves the token for you, and your Pythe session is never touched.
Two levels
| Level | Access | Used for |
|---|---|---|
| Connect | Your name, email and profile. | Knowing which Google account is connected. |
| Enable sending | Adds permission to send email on your behalf. | Outreach emails you approve. Re-asks for consent if you had already connected. |
Connect and enable sending
- Open Connectors. Choose Google, then Connect. Or press Connect Gmail on a card in a chat. You come back to the same chat.
- Pick the account. It can be a different Google account from the one you sign in to Pythe with.
- Approve. Choose Continue if Google warns about a new app.
- Enable sending. Choose Enable sending when you want your Outreach employee to send. Google asks once more for permission.
What sending looks like
- Every email is an approval first. You see the recipient, subject and body, and can edit.
- Emails come from your own address, with a sign-off and an opt-out line.
- Daily caps: 0 on Free, 50 on Base, 200 on Premium, resetting at midnight UTC.
- On Premium you can turn on autopilot for Gmail per employee.
Related
Previous: Connectors overview · Next: Stripe, PostHog and what to measure