How to Parse Emails in Make (Integromat): A Practical Guide
Last updated July 2026
Try it now: extract email data to Excel, CSV, or JSON
Connect a mailbox to pull .eml/.msg in bulk, or paste a raw email to test the converter now.
Create a free account to download. No credit card required.
Turn inbound email into structured fields
MailParse reads the fields you name from any email and returns them as clean data you can route in Make. See the email parser API, or read the walkthrough below.
Last updated July 2026
Make (formerly Integromat) is a strong no-code automation platform, and one of the first things teams try to build in it is a scenario that reads an incoming email and does something with the data inside. That works well for the routing, and it gets harder the moment you need a specific value out of the message body. This guide covers both halves honestly: what Make does natively and where a dedicated parser earns its place.
Can Make parse an email?
Partly. Make can watch a mailbox with its Email or Gmail modules, trigger on each new message, and give you the sender, subject, and body as text. Pulling a specific value out of that body, such as an order number or invoice total, is where it gets manual: you use a Text parser module with a regular expression you write and maintain, or hand the raw email to a parsing service that returns named fields. Make handles the trigger and the routing; the field extraction is the part to plan.
How to parse an email in Make, step by step
The pattern is the same whichever extraction method you pick. Only the middle module changes.
| Step | Module | What it does |
|---|---|---|
| 1. Trigger | Email / Gmail: Watch emails | Fires on each new message and outputs the sender, subject, and body |
| 2. Extract | Text parser, or an HTTP call to a parser API | Pulls the named values out of the body, by regex or by field name |
| 3. Route | Sheets, database, CRM, or webhook module | Writes the fields where you need them |
Module names as of July 2026. Verify the current Make module set before you build.
How do I extract a specific field from an email body in Make?
Use the Text parser module with a regular expression, or call a parser API that returns the field by name. The regex route is free and native, but it is keyed to the exact wording and position in the email, so it breaks when a sender reorders lines or changes a label. Naming the field with a parser instead means the value is found across layouts, which is the difference between an automation you set once and one you keep patching.
When should you use a dedicated email parser with Make?
Reach for a parser when the emails vary or contain tables. If every message is identical, a Make regex is enough. But order confirmations, invoices, and lead emails differ between senders, and many carry an HTML table of line items that regex handles badly. A parser reads named fields across those layouts and turns table rows into separate records, then hands Make clean data to route. You keep Make for what it is best at, connecting apps, and stop maintaining fragile match patterns.
Can Make read data inside an email attachment?
Not the contents on its own. Make can download an attachment and pass the file to another service, but neither Make nor MailParse reads the data inside a PDF or spreadsheet attachment directly. MailParse parses the email body and its HTML tables into named fields and lists each attachment by filename and type. If the value you need lives inside an attached document, add a document extraction step for that file and merge its output with the parsed email in your scenario.
How do I send parsed email data onward from Make?
Once the fields are structured, Make routes them with a module for almost any destination: append a row to Google Sheets, insert into a database, create a CRM record, or POST to a webhook. This is Make's core strength. For vendor bills and order emails, that downstream step often feeds a system that automates purchase orders and approvals, so the parser reads the email and Make delivers the fields to the tool that acts on them.
Where this fits
Parsing email in Make is one automation pattern among several. If you would rather skip the scenario entirely, a parser can connect the mailbox and export a spreadsheet or POST JSON on its own. For the endpoint and webhook details, see the email parser API, and if you build on a different platform, the same approach applies to parsing emails in n8n. For a primer on what parsing does before you wire it up, start with what is email parsing.