Email parser for Outlook: inbox rules, Power Automate or a dedicated parser

Outlook can forward and trigger flows, but it does not extract fields

An email parser for Outlook is either a dedicated parsing tool fed by an Outlook inbox rule, or a Power Automate flow that you build yourself, because Outlook on its own does not pull fields out of messages. The job is the same in both cases: when an order, lead or invoice email arrives in an Outlook or Microsoft 365 mailbox, capture the values you need and write them to Excel or another system.

Microsoft's documentation covers both routes. The right one depends on whether you already use Power Automate, and on whether your data sits in the email body or in attachments.

Outlook inbox rules: forward versus redirect

Microsoft's support page describes two rule actions. A forwarded message appears to come from you, and replies go back to your address. A redirected message appears to come from the original sender. If you want the parser to capture who sent the email, redirect is the better choice. Either works if you use the same one consistently.

1. In new Outlook, open Settings, then Mail, then Rules, and select Add rule.
2. Name the rule and add a condition. Microsoft's example uses Apply to all messages, but for parsing a narrower condition is safer.
3. Add the action Forward to, Forward as attachment or Redirect to, and enter the parser's inbox address.
4. Save. Optionally select Stop processing more rules.

Classic Outlook has the same options under Manage Rules & Alerts. If forwarded mail does not arrive, check that forwarding is allowed on the account: Zapier's help page notes that email forwarding has to be enabled before Outlook will auto-forward to a parser.

Power Automate with the Office 365 Outlook connector

Power Automate's Office 365 Outlook connector has a trigger called When a new email arrives (V3). Microsoft's guide shows it filtering on From, To, CC, importance, Has Attachment and a subject filter, and recommends filtering in the trigger because every run counts against your plan's run quota. You need a Power Automate account and an Outlook for Microsoft 365 or Outlook.com mailbox.

The trigger hands you the message and, if you turn on Include Attachments, the files. Extraction is then up to you. For invoices, Microsoft's AI Builder has a prebuilt invoice processing model that can be used in Power Automate. It accepts JPEG, PNG or PDF files up to 20 MB and returns fields such as invoice ID, invoice date, due date, vendor name and invoice total.

Microsoft lists known limits: when many emails arrive at once, the trigger can occasionally miss some, and emails with attachments can time out while the files download. Build a check for that. Our page on the exception queue describes one.

When a dedicated parser is simpler than a flow

If your organization already uses Power Automate and someone can maintain flows, the Microsoft route keeps the work in tools you already have. If nobody wants to own a flow, a parser is quicker to set up. Parsio prices as read on 3 October 2026 on monthly billing: Starter at $29 for 100 credits or $49 for 1,000 credits, Growth at $149 for 5,000 credits.

A worked example, one limitation and an alternative

Suppose an Outlook mailbox receives 200 web-form lead emails and 60 one-page supplier invoices a month. In Parsio, the leads go through the template parser at 1 credit each (200 credits) and the invoices through the AI parser at 3 credits a page (180 credits). The 380 credits fit the 1,000-credit Starter option at $49 a month, or $41 a month billed annually. If credits run out, new mail is received but not parsed until the next period.

The limitation that matters: Parsio's one-click Outlook connection imports existing emails. For new mail going forward, its help center tells you to set up a forwarding rule, so the route depends on forwarding being allowed on your account. If it is not, Power Automate is the workable route. A second alternative is Email Parser from emailparser.com, which connects to Office 365 and Exchange accounts directly at $25 a month for its web app. See how to parse emails step by step and the Parsio integrations page for what happens after extraction.