Parse Gmail emails and attachments automatically
Set up a Gmail filter, forward matching emails to Parsli, and every invoice, receipt, order, or confirmation becomes structured data in your Sheet, QuickBooks, CRM, or API. Read-only access, no rules to maintain, no Zapier middleware.
Get Started FreeWhat Gmail auto-forwarding does for document workflows
Gmail is Google Workspace's email client, used by over 2 billion accounts worldwide. Most business-critical data — vendor invoices, order confirmations, lead notifications, shipping updates, booking confirmations — lands first in somebody's Gmail inbox. The challenge is never "receiving" the data; it's getting that data out of the email and into the systems where decisions actually happen.
Gmail has two features that make this possible: filters (rules that match emails by sender, subject, or content) and auto-forwarding (send matching emails to another address without user action). Combined, they let you route any subset of your inbox — "everything from @acme.com with an attachment", "anything mentioning 'Invoice' in the subject" — to a downstream service that does the actual extraction work.
That downstream service is where Parsli fits. Parsli gives each parser a unique inbox address; Gmail's auto-forwarding rule sends matching emails there; Parsli's AI extracts every field you defined and pushes the structured data to wherever you need it.
Why Parsli + Gmail replaces manual inbox processing
The old workflow: someone on your team opens Gmail every morning, finds the invoice emails from vendors, downloads each PDF, opens Excel or QuickBooks, retypes the vendor name, amount, date, line items, and PO number. For a business handling 200 invoices a month, this is roughly 15–20 hours of pure data entry — before you count mistakes, missed invoices, and the people-tax of interrupting people to process emails.
The new workflow: you create a Gmail filter that auto-forwards invoice emails to a Parsli inbox address. Parsli reads both the email body AND any PDF attachments, extracts every field defined in your schema, and routes the data to QuickBooks (native), Google Sheets, your CRM, or an API. A new vendor starts sending invoices in a layout you've never seen — Parsli still extracts them correctly, because the AI adapts without templates.
The Gmail side stays exactly the same as you'd set up for any other forwarding workflow. The extraction and routing side is the part that used to require custom code or brittle template tools. Parsli replaces that layer.
How to Set Up
Get your Parsli inbox address
Each parser you create in Parsli has a unique address like parser-abc@parsli.co. You'll find it in your parser's Import tab under Email forwarding.
Create a Gmail filter
In Gmail, Settings → Filters and Blocked Addresses → Create a new filter. Set the match criteria: from:(*@vendor.com), has:attachment, subject:(Invoice), or any combination. Click Create filter.
Enable auto-forward on the filter
In the "Also apply the filter to matching messages" page, check "Forward it to:" and paste your Parsli inbox address. Gmail will require you to verify ownership of the destination address — Parsli handles that automatically.
Verify and activate
Parsli confirms receipt of Gmail's verification email. Activate the filter. Every matching email (going forward, and optionally historic) gets processed. Extracted data flows to the destinations you configured in the parser.
Walkthrough: auto-forward vendor invoices from Gmail into QuickBooks
You're the controller at a 30-person firm. Vendors email PDF invoices to ap@yourcompany.com (a Gmail-hosted address). Today, you download each PDF and type the data into QuickBooks Bills. You want every invoice to post as a QuickBooks Bill automatically, with the PDF attached, without touching any email.
- 1
Create an Invoice parser in Parsli
In Parsli's dashboard, New Parser → Invoice template. The parser comes with fields pre-defined: vendor_name, invoice_number, invoice_date, due_date, total, line_items. Add or remove fields to match your accounting needs. Save.
- 2
Connect QuickBooks as the destination
Open the parser's Integrations tab, click Add Integration → QuickBooks. OAuth redirects you to Intuit, you pick your QuickBooks company, and you're back in Parsli. Choose the default expense account and whether to auto-create missing vendors (off by default — safer).
- 3
Copy your Parsli inbox address
Go to the parser's Import tab. You'll see a unique email address (e.g., vendor-invoices-abc@parsli.co). Copy it.
- 4
Set up the Gmail filter
In ap@yourcompany.com's Gmail, Settings → Filters → Create a new filter. Match: has:attachment from:(-*@yourcompany.com). This catches any inbound email with an attachment that wasn't sent by your own domain. Click Create filter → "Also forward to:" → paste the Parsli inbox address. Gmail sends a verification email; Parsli confirms it automatically.
- 5
Test with one real invoice
Have a vendor send you an invoice (or forward yourself an existing one into ap@). Within 5 seconds, Parsli receives it; within another ~10 seconds, the extraction completes; within ~15 seconds total, a Bill appears in QuickBooks with the original PDF attached. Verify it's correct, then let the filter run on live inbound email. You'll never retype another vendor invoice.
- 6
Add a review queue for safety (optional)
In Parsli's parser settings, set a confidence threshold (e.g., 90%). Extractions above that auto-post to QuickBooks; below goes to a review queue. You review low-confidence extractions once a day — usually 5–10% of volume — and approve or correct before they post. Keeps the hands-off workflow without losing control.
What teams build with Parsli + Gmail
Vendor invoices → QuickBooks Bills
Any invoice email (PDF attached or body-only) becomes a QuickBooks Bill with the original PDF attached. No Zapier, no middleware.
See the workflowOrder confirmations → CRM
Shopify, WooCommerce, Amazon, Etsy order emails become structured order records in HubSpot or your CRM. Customer name, order ID, items, amount — all extracted.
See the workflowLead-form emails → CRM contact
Your website's contact form sends emails; Parsli extracts name, email, company, inquiry topic, and pushes a structured lead into HubSpot or Salesforce.
Shipping confirmations → ops tracker
FedEx, UPS, DHL shipping notifications become rows in a Sheet with tracking number, ETA, and destination — live visibility without custom integrations.
Receipt emails → expense records
Travel-booking emails (hotels, flights, rentals), retail receipt emails, and SaaS invoices become expense records with merchant, date, amount, tax, and category.
See the workflowParsli via Gmail forwarding vs. Zapier Email Parser on the same inbox
| Criterion | Parsli | Zapier Email Parser |
|---|---|---|
| Extraction method | AI (Gemini 2.5 Pro) | Pattern/template matching |
| Handles layout changes | Automatic | Template breaks silently |
| Reads PDF attachments | Yes | No |
| Reads scanned / photo attachments | Yes (built-in OCR) | No |
| Line-item tables | Native | Single-field only |
| Setup per new sender | Zero (one schema covers all) | New template per sender |
| Works with Gmail's native filters | Yes (standard forward rule) | Yes, but extraction is weaker |
| Accuracy on real-world vendor invoices | 95%+ | ~75% and drops on format changes |
Why Use Gmail with Parsli
- **Uses Gmail's native auto-forward rule** — no Gmail add-in, no plugin, no Workspace admin changes
- **Read-only Gmail access** (if you connect the direct integration instead of forwarding) — Parsli cannot send, delete, or modify emails
- **Works with any Gmail account** — personal, Workspace, custom domains, shared inboxes
- **Filter by any Gmail criterion** — sender, subject, has-attachment, label, search query
- **Processes body AND attachments** — unlike Zapier's parser, which only reads the body
- **No per-sender template** — one parser + one filter covers all vendors, regardless of invoice layout
- **Verification is automatic** — Parsli confirms Gmail's forward-verification email without manual intervention
- Pair with [QuickBooks](/integrations/quickbooks) or [Google Sheets](/integrations/google-sheets) for a full inbox-to-system-of-record pipeline — [no code required](/guides/extract-data-from-pdfs-without-code)
Frequently Asked Questions
Do I need the Gmail integration or can I just set up a forward rule?
Either works. A plain Gmail forward rule (Settings → Filters → Forward to Parsli's inbox address) is the simplest — no OAuth, no permissions — and it covers 90% of use cases. The direct Gmail integration is useful when you want to process historic emails, filter by Gmail label (not just sender/subject), or avoid forward-rule limits on certain Workspace policies.
Is my Gmail data safe?
Yes. If you use the forward rule approach, Parsli never touches your Gmail account directly — it just receives the emails you explicitly forward. If you use the direct Gmail integration, Parsli requests read-only access (Google's gmail.readonly scope). We cannot send, delete, modify, or organize your emails. Only attachment binaries and email content needed for extraction are read, and only for the emails matching your filter.
How fast is extraction after an email arrives?
Typically 3–15 seconds end-to-end: Gmail forwards the email (~1 second), Parsli receives and parses it (~3–10 seconds depending on attachment size and complexity), and pushes to destinations (QuickBooks, Sheets, etc. in under 5 seconds). Real-time enough for most operational workflows.
Can I process emails from multiple senders or filter rules?
Yes. Two approaches. One parser per document type (Invoices, Receipts, Orders) with separate Gmail filters forwarding each kind to a different Parsli inbox. Or one parser catching everything and using the extracted data's fields to branch downstream (e.g., if vendor_name is in your Approved list, auto-post to QuickBooks; else send to review queue). Most teams use the first pattern — it's cleaner and more maintainable.
What about Gmail's verification email?
When you set up forwarding in Gmail, Google sends a verification code to the destination address to confirm ownership. Parsli automatically reads the verification email and confirms — you don't need to manually click a link. Takes under 60 seconds from the time you set up the filter.
Does it work with Gmail labels?
The direct Gmail integration can filter by label (e.g., process only emails in the "AP" label). The forward-rule approach uses Gmail filters that support label-based matching too — just set the filter to match "has: the label:AP" and forward those. Both paths work; the direct integration is slightly more flexible for complex label logic.
What email types are supported?
Any email Gmail receives — standard SMTP emails, emails with PDF/image/Word/Excel attachments, body-only emails (order confirmations, lead forms, notifications), HTML emails with embedded data, plain-text emails. Parsli's AI reads subject, from/to/cc, body, and every attachment in one extraction pass.
Can I use this with multiple Gmail accounts?
Yes. Set up forwards from each account to the same Parsli parser's inbox address. All emails flow to the same parser, get extracted the same way, and route to the same destination. Useful for teams where vendor invoices come to multiple people's inboxes — all normalize into the same AP pipeline.
Used in these workflows
See how teams actually use Gmail with Parsli end-to-end.
Extract Data from Emails
Set up an inbound email address, forward business emails (orders, leads, confirmations, vendor invoices), and get structured data in the system of record — QuickBooks, Sheets, CRM, or your API. No templates.
Parse Invoices to QuickBooks
Forward vendor invoices, and every field — vendor, amount, line items, due date — lands in QuickBooks Online as a Bill with the PDF attached. No Zapier, no templates, no copy-paste.
Email Parsing
Turn incoming emails into structured data automatically. Parsli connects to your Gmail inbox and extracts data from email bodies and attachments in real-time.
Invoice Parsing
Stop manually entering invoice data. Parsli extracts vendor names, amounts, line items, due dates, and more from any invoice format — PDF, image, or email attachment.
Pairs well with
Parsli can fan out the same extracted data to multiple destinations — these integrations commonly run alongside Gmail.
QuickBooks Online
Parsli's native QuickBooks integration turns any invoice, bill, or receipt into a QuickBooks Bill, Expense, or Invoice automatically — with the original PDF attached. No Zapier, no Make, no templates. Connect in under 60 seconds and watch your AP inbox empty itself.
Google Sheets
Paste one IMPORTDATA formula into a Google Sheet and every document Parsli parses — PDFs, invoices, bank statements, emails — appears as a new row. No Zapier, no middleware, no manual export.
Outlook
Create an Outlook rule that auto-forwards invoice, order, or confirmation emails to Parsli. The AI extracts every field from the body and all attachments, then routes the structured data to QuickBooks, Google Sheets, or your API. No Outlook add-in, no IT involvement.
Zapier
Use Parsli to extract structured data from any email or document, then use Zapier to route the data to any of 5,000+ apps — CRMs, databases, project tools. Parsli replaces Zapier's built-in Email Parser with real AI; Zapier handles the routing.
HubSpot
Turn incoming emails and documents into HubSpot contacts automatically. Parsli extracts name, email, company, phone, and custom fields — then pushes them to HubSpot CRM via Zapier or Make.
Webhooks
Full webhook support for both sending documents to Parsli and receiving extracted data. Connect to any HTTP endpoint with standard authentication options.