Parse Outlook emails and attachments with AI
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.
Get Started FreeWhat Outlook's forwarding and rules can — and can't — do
Outlook (both the Microsoft 365 web/desktop version and Outlook.com) is the default business email client in most enterprises. It ships with a powerful Rules engine: you can run rules when mail arrives, match by sender, subject, body text, attachment presence, importance, or combinations, and trigger actions like move-to-folder, categorize, or forward.
What Outlook Rules cannot do is read the email and turn it into structured data. A rule can tell you "this invoice arrived from Acme", but it can't extract the invoice total, due date, or line items. For any workflow that needs structured data downstream — posting a Bill in QuickBooks, updating a HubSpot deal, appending a row to a reporting Sheet — you need an extraction layer after the rule fires. That's the piece Parsli provides.
Outlook auto-forwarding is also commonly restricted by tenant admins for security reasons (preventing inadvertent data leaks). The workaround is almost always to forward to an approved internal service. Parsli can operate as that approved service: each parser has a unique address on the parsli.co domain that IT can allowlist once, then the forward rule works for every user.
Why Parsli + Outlook replaces manual inbox processing
In most finance, ops, and sales teams, Outlook is where the work starts and ends. Invoices arrive in a shared mailbox. Order confirmations pile up in the ops team's inbox. Lead-form emails route to sales. Every one of these is structured data trapped inside an email — and someone, somewhere, is retyping it into a downstream system.
Parsli connects to Outlook via the same forwarding pattern you'd use to route emails anywhere: a Rule that matches by sender, subject, or content, and forwards to the parser's unique Parsli address. Parsli's AI reads body + attachments (PDFs, Word, Excel, images — all supported), extracts every field defined in your parser's schema, and pushes the structured data to your destinations. No Outlook add-in, no Office script, no PowerShell, no IT approval beyond the initial domain allowlist.
For enterprise setups where auto-forwarding is restricted, the pattern also works via Microsoft Power Automate — Parsli integrates with Power Automate flows for tenants that prefer governed automation over Outlook Rules. See /integrations/power-automate.
How to Set Up
Get your Parsli inbox address
Each parser has a unique Parsli inbox address (e.g., invoices-abc@parsli.co) shown in the parser's Import tab. Copy it.
Create the Outlook rule
Outlook → Settings (gear icon) → Mail → Rules → Add new rule. Set conditions: from:(specific senders), subject contains "Invoice", has attachment, or any combination. Action: "Forward to:" → paste the Parsli address. Save.
Verify forwarding if needed
If your tenant requires verification for external forwards, approve the one-time verification email Parsli receives. Your IT admin may need to allowlist parsli.co in the Exchange transport rule.
Run it on your inbox
Test by sending (or forwarding) one matching email. Within 5–15 seconds, Parsli extracts every field and pushes the data to your configured destinations (QuickBooks, Sheets, webhook). Review the first few extractions; then let the rule run on live traffic.
Walkthrough: auto-forward vendor invoices from Outlook 365 shared mailbox to QuickBooks
You run AP in a 200-person firm. Vendor invoices flow into ap@yourcompany.com, a shared Outlook 365 mailbox. Today, the AP clerk downloads each PDF and types it into QuickBooks Bills. You want every invoice to post automatically, with the PDF attached, and without asking IT for add-ins or Power Automate licenses.
- 1
Ask IT to allowlist parsli.co (one-time)
If your tenant blocks external auto-forwards, have IT add a Exchange transport rule allowing forwards to *@parsli.co. One tenant-level change; never needs touching again. If your tenant permits external forwards freely, skip this step.
- 2
Create an Invoice parser in Parsli
New Parser → Invoice template. Add your required fields: vendor_name, invoice_number, invoice_date, due_date, total, line_items. Connect QuickBooks via the Integrations tab — OAuth into Intuit, pick your company, choose the default expense account.
- 3
Copy the Parsli inbox address
In the parser's Import tab, copy the unique Parsli inbox address (e.g., ap-invoices-xyz@parsli.co).
- 4
Create the Outlook rule on the shared mailbox
Open ap@yourcompany.com in Outlook → Settings → Rules → Add new. Name: "Forward vendor invoices to Parsli". Condition: has attachment AND (NOT from:*@yourcompany.com) — catches external senders with attachments. Action: Forward to ap-invoices-xyz@parsli.co. Also: Stop processing more rules (optional, prevents other rules from duplicating work). Save.
- 5
Test end-to-end with one real invoice
Have a vendor send an invoice to ap@ — or forward one yourself. The rule fires, Parsli receives the email + PDF, extracts every field, creates a QuickBooks Bill with the PDF attached as an Attachable. Open the Bill in QuickBooks to verify vendor, amount, line items. Tweak the parser schema if any field extracted incorrectly (the AI adapts automatically for the next email — no re-training required).
- 6
Monitor and tune
For the first week, keep the parser's confidence threshold set to Medium — extractions above auto-post to QuickBooks, below goes to Parsli's review queue. After a week of clean data, raise the threshold or enable fully-automatic posting. Most teams end up with 85–95% of invoices going hands-off within 2 weeks.
What teams build with Parsli + Outlook
Shared AP mailbox → QuickBooks
ap@, accounts@, or invoices@ shared mailboxes route vendor invoices directly into QuickBooks Bills with PDFs attached. Works for Outlook 365, Exchange Server, Outlook.com.
See the workflowSales inbox → CRM leads
Inquiry emails from your website's contact form or sales@ mailbox become structured HubSpot/Salesforce leads — contact name, company, inquiry topic, amount.
See the workflowOps inbox → shipment tracker
Carrier shipment confirmations (FedEx, UPS, LTL) land in a shipping Sheet with tracking number, ETA, origin, destination — no manual entry, no missed deliveries.
Shared travel inbox → expense records
Concur, TripActions, Expensify travel-booking emails become expense records with itinerary, amounts, payment method — ready for reimbursement approval.
See the workflowSupport inbox → ticket data
Customer emails flow to a structured ticket view — subject, customer email, product mentioned, urgency — without touching Zendesk or Freshdesk.
Parsli via Outlook forwarding vs. Outlook add-in approach
| Criterion | Parsli | Outlook add-in (e.g., Power Automate / 3rd-party) |
|---|---|---|
| Requires add-in installation | No — standard forward rule | Yes — per-user deploy or tenant-wide |
| Requires IT approval | One-time domain allowlist (if tenant blocks external forwards) | Add-in review, license, deployment |
| Works on shared mailboxes | Yes (Rules support shared mailboxes) | Often complicated — per-mailbox licensing |
| Works on mobile Outlook | Yes (rule runs server-side) | Rarely — most add-ins are desktop-only |
| Extraction method | AI (Gemini 2.5 Pro) | Varies by add-in |
| Handles attachment layouts | Any (PDF, images, Word, Excel, scans) | Depends heavily on add-in |
| Per-user cost | One Parsli plan covers all forwarding users | Often per-seat add-in licensing |
Why Use Outlook with Parsli
- **No Outlook add-in, no plugin, no admin install** — standard Outlook Rule with Forward action
- **Works on Outlook 365 web, desktop, Outlook.com, and Exchange Server** — the Rules engine is consistent across all
- **Shared mailbox friendly** — Rules on shared mailboxes forward exactly like a personal mailbox
- **Mobile-safe** — server-side rules fire regardless of whether anyone has Outlook open
- **Processes body AND every attachment** — PDFs, Word, Excel, images — in one extraction
- **AI handles format changes** — vendors redesigning invoices doesn't break anything
- **Parallel with Power Automate** — teams with governed automation can use /integrations/power-automate as the pipeline instead of direct forwards
- Pair with [QuickBooks](/integrations/quickbooks), [Google Sheets](/integrations/google-sheets), or your [CRM](/integrations/hubspot) for end-to-end automation
Frequently Asked Questions
Do I need to install an Outlook add-in?
No. Parsli uses standard Outlook Rules with a Forward action. You configure one rule per mailbox (or a shared-mailbox rule), point it at your unique Parsli inbox address, and you're done. No add-in to review, no AppSource approval process, no per-seat cost.
My tenant blocks external auto-forwarding. What do I do?
Many Microsoft 365 tenants have transport rules that block external auto-forwards for security. Two options: (1) Ask IT to add an Exchange transport rule allowing forwards to *@parsli.co specifically — a targeted exception that doesn't compromise the general policy. (2) Use the Power Automate integration instead (see /integrations/power-automate). Power Automate flows are tenant-governed and often pre-approved where direct forwards are blocked.
Does this work with shared mailboxes?
Yes. Outlook Rules on shared mailboxes (ap@, sales@, support@) fire exactly like rules on personal mailboxes. The forward action triggers regardless of who is reading the mailbox at the time. This is actually the preferred pattern for team workflows — set up one rule on the shared mailbox; all team members' interactions with the mailbox are covered.
What about Outlook.com (personal) accounts?
Works identically. Outlook.com has the same Rules engine. Create a rule, add a Forward-to action pointing at your Parsli address, save. The only difference vs. Microsoft 365 is that personal Outlook.com tenants don't have admin-level transport rule restrictions, so external forwards usually just work without IT involvement.
What attachments can Parsli read?
Every common business attachment: PDF (native and scanned), images (PNG, JPG, HEIC from iPhone), Word (.docx), Excel (.xlsx), plain text, and even embedded signatures in HTML emails. The AI reads the full email body and every attachment as one logical document, then extracts to your schema.
How do I handle emails without attachments (body-only data)?
Set up your parser's schema to pull from email body fields. Order-confirmation emails (Shopify, Amazon), booking confirmations, and lead-form emails all carry their data in the body itself. Parsli's AI is schema-first: tell it what fields you want, it finds them in whatever content is present — body, attachment, or both.
Is there a delay between the rule firing and data appearing?
Typically 3–15 seconds end-to-end. Outlook fires the forward rule near-instantly (sub-second for cloud mailboxes). Parsli receives, extracts, and pushes to destinations within the remaining window. For operational workflows, this is effectively real-time; for reconciliation workflows, latency is irrelevant.
What if my team is split across Outlook and Gmail?
No problem. Set up forward rules on each — Outlook Rules for the Outlook users, Gmail Filters for the Gmail users — all pointing at the same Parsli parser's inbox address. Everything normalizes into the same extraction schema and downstream destination. See /integrations/gmail for the Gmail side.
Used in these workflows
See how teams actually use Outlook 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-to-Database Workflow
The end-to-end workflow that takes a message from a sender's outbox to a clean row in your destination system — and the rules that decide what slips through automatically and what hits your review queue.
Pairs well with
Parsli can fan out the same extracted data to multiple destinations — these integrations commonly run alongside Outlook.
QuickBooks Online
The native QuickBooks Online integration AP teams use as a QuickBooks receipt scanner and bill-posting engine. AI reads invoices, vendor bills, and card receipts, then creates QuickBooks Bills, Expenses, or Invoices with the source PDF attached. No Zapier middleware, no per-vendor templates. Connect over Intuit's official OAuth in under 60 seconds.
Power Automate
Build enterprise document processing flows with Microsoft Power Automate. When Parsli extracts data from a document, the webhook triggers your Power Automate flow — routing data to SharePoint, Dynamics 365, Teams, or any Microsoft 365 app.
Gmail
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.
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.
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.