Setup
How to connect a Gmail mailbox to MAILTIG
OAuth scopes MAILTIG requests, what the connection can send and receive, and why the button stays disabled until an operator configures Google.
By MAILTIG editorial. Reviewed by Engineering (Integration engineer (product source)) on 4 November 2026. Next review due 4 February 2027. 6 minute read.
MAILTIG connects a Google mailbox with OAuth. It does not ask for your Google password.
Scopes requested
openid, email, gmail.send, gmail.readonly, with offline access and a consent prompt. Send uses Gmail's users/me/messages/send. Replies are polled about once a minute (the newest 25 inbox messages per run). Tokens refresh two minutes before expiry.
Before the button appears
The MAILTIG operator must configure a Google OAuth client ID and secret. Until that is done, the OAuth button in the product is disabled. This is intentional: a missing client would send people into a broken Google consent screen.
After you connect
- MAILTIG creates or updates the mailbox, stores encrypted tokens, and marks it Connected.
- Daily send limit defaults to 50. Google's own quota still applies and is usually the tighter cap.
- DKIM is handled by Google. You still need a verified sending domain in MAILTIG so preflight can pass.
- Replies appear in the unified inbox when they match a campaign message or a known contact.
If refresh fails, the product tells you to connect the mailbox again. There is no push (Gmail watch) yet; replies arrive on the poll.