Integrations · Email

Connect Gmail to Well

Well scans your Gmail inbox for invoices and receipts, extracts all fields with AI, and organizes everything in your workspace automatically.

Active in production

Production adoption for the Gmail connector

On Gmail
66workspaces
Live on Gmail in production since October 2025.
30% also use Google Drive
Most common tool connected alongside Gmail.
Travel & transport · Bank, FX & payment-processing fees · Business & productivity software
Most-matched categories for Gmail records.
13,555
Invoices processed to date across Gmail workspaces.
98%
Auto-post-ready across Well, to date.

Adoption figures for Gmail · updated 2026-06-19. Auto-post-ready % is a platform-wide rate across all of Well, to date (confidence ≥ 0.85). Numbers anonymised; no customer identifying data.

What Well pulls from Gmail

Gmail feeds invoice email, receipt, sender into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Gmail’s access.

From GmailIn Well
Invoice email
Invoice document
Receipt
Expense
Sender
Vendor
Thread
Audit trail
Gmail logo
Sync mode
incremental polling
Refresh
scheduled
Direction
Gmail → Well

6 triggers from Gmail.

  • When an invoice PDF arrives as an attachment

    Picks up emails matching has:attachment filename:pdf and runs the document through extraction.

    Trigger·Invoice
  • When an email with an invoice attachment is received

    Well picks up any received email with a PDF attachment; forwarded headers are recovered automatically.

    Trigger·Invoice
  • When an email attachment is processed by Well

    Receipts, invoices, statements: any PDF attachment is read and captured into your records.

    Trigger·Document
  • When an email with a bill attachment is processed by Well

    Well's AI extracts the bill from the attached PDF and matches the vendor against your existing records.

    Trigger·Invoice
  • When an email arrives from a sender domain already in your vendor list

    The vendor is matched against your existing company records.

    Trigger·Invoice
  • When an email arrives from a sender domain not yet in your vendor list

    Well prepares a new vendor record from the email and document headers for your confirmation.

    Trigger·Invoice

What Well does with your Gmail connection

Connect

Connect Gmail over OAuth 2.0 (Gmail scope): you grant read-only mailbox access on Gmail's consent screen, so the password never reaches Well; Well holds only a scoped read token.

Sync

Well brings invoice email, receipt, and sender in from Gmail on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Gmail entity into invoice document, expense, and vendor, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Gmail lands in the workspace as invoice document, expense, and vendor you can search, chart, and automate.

Questions Gmail unlocks

Ask in plain language. Well answers from your connected Gmail connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Gmail connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Gmail connection…

Connect Gmail in three steps

  1. 01

    Sign in to Gmail read-only

    Choose Gmail in Well's Connections panel and sign in with Google. Well requests the gmail.readonly scope plus basic profile, which you grant on Google's own consent screen. No password or key is stored in Well; Google issues a read-only token.

    • AuthGoogle OAuth 2.0
    • Scopegmail.readonly (read-only)
    • TransportGmail REST API
  2. 02

    Map your entities

    Well scans your inbox for messages with invoice and receipt PDFs, reads those attachments through the Gmail API, and extracts vendor, amounts, tax, dates, and line items, keeping the sender, subject, and date headers for traceability.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    The extracted documents become structured records you can query, match, and route to a connected accounting destination. Gmail stays read-only throughout, so Well captures and structures but never sends or changes anything in your mailbox.

    • First syncstarts as soon as connect completes

Sign-in takes about a minute. Recent mail is read first; your earlier inbox backfills in the background while you work. Gmail developer docs.

How Gmail stays secure with Well

Gmail connects through Google OAuth 2.0 with the read-only gmail.readonly scope, read over the Gmail REST API, so Well receives a token that can read messages and attachments and cannot send, delete, or label mail. Well uses it to find invoice and receipt PDFs and extract their fields; the mailbox stays untouched. Read-only is the whole grant, and there is no write path to misuse.

OAuth 2.0 (Gmail scope)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requests
  • Read Gmail records

    Endpoints the Gmail API token grants, scoped by your consent.

    granted
  • Resolve invoice email, receipt, sender, and thread across your stack

    Match identifiers in Gmail against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Gmail records

    Not granted; Gmail is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Gmail passwords or session cookies

    Authentication runs through OAuth 2.0 (Gmail scope) tokens we never see.

    refused
Disconnect any time from Well settings or Gmail’s admin panel.

Frequently asked questions about Gmail and Well

Select Gmail in Well's Connections panel and sign in with Google. Well requests the read-only gmail.readonly scope plus your basic profile, which you approve on Google's consent screen. That scope lets Well read messages and attachments and nothing else; it cannot send, delete, or label mail on your behalf.

Well scans your inbox for messages carrying invoice and receipt PDFs, reads those attachments through the Gmail API, and extracts the vendor, amounts, tax, dates, and line items into structured workspace records. It also keeps the sender, subject, and date headers so each captured document traces back to the email it came from. The PDF is the payload; the headers are the audit trail.

Well's interest is messages with invoice and receipt attachments, so the documents it captures are the financial ones; ordinary correspondence is not turned into workspace records. The grant is the standard read-only mailbox scope, which is the access Gmail offers for reading mail, and Well uses it to find and extract the documents that matter, not to mine your conversations.

Well reads PDF invoices and receipts directly, and its document understanding handles scanned images and photographed paper documents as well as cleanly generated PDFs. A receipt buried in the email body or sent as an image is extracted the same way a structured PDF is. The output is a structured record regardless of how the original was produced.

Well reads recent mail through the Gmail API in the background and captures invoice and receipt attachments as it finds them, while the first connect works back through your existing inbox. Documents that have been read are queryable while the backfill continues. Gmail stays your mailbox; Well holds the extracted documents beside the rest of your records.

Disconnect Gmail in Well and the Google token is revoked, so Well stops reading your mailbox at once. Because the scope was read-only, there was never any send or change to unwind. The invoices and receipts Well already extracted stay in your workspace so past questions keep answering; ask Support if your retention policy needs them removed.

Gmail logo

Ready to connect Gmail?

Connect once. Every invoice email, receipt, sender from Gmail becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.