Zapier Email Parser and Zapier Mail Parser: How It Works, the 15 Template Limit, and What to Use Instead
Zapier parses email by memorizing where a value sat in one sample message. Here is what that buys you, and where it breaks.
Email Parser by Zapier is the fastest way to get a value out of a predictable email and into a Zap. You forward one message to a @robot.zapier.com address, highlight the order number, and every future message from that sender gives you an order number field. The trouble starts when the mail is not predictable: HTML tables, a redesigned notification, several layouts in one mailbox, or more than 15 templates. This page covers the setup, the documented limits, what it really costs, and the point where a parser that reads the whole message beats one that memorizes coordinates.
Last updated August 2026
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.
Email Parser by Zapier gives you a mailbox at @robot.zapier.com, then asks you to send it one sample message and highlight the values you want. It saves those highlights as a template and matches every later email against the same surrounding text. It is bundled with a Zapier account, and Zapier documents a ceiling of 15 templates per mailbox. The matching is positional rather than semantic, so when a sender changes their layout the template stops matching and the Zap goes quiet without an error.
- 15
- Templates per Zapier parser mailbox
- @robot
- Mail goes to a robot.zapier.com address
- Per task
- The real cost is the Zap tasks it fires
- No template
- MailParse names fields instead of coordinates
Email Parser by Zapier is a genuinely useful free-with-your-account tool, and most guides about it skip the part that decides whether it will work for you. It is worth being precise. You create a mailbox, Zapier issues an address ending in robot.zapier.com, and you send one representative email to it. In the browser you highlight the words you care about and give each one a label: order_number, customer_email, total. Zapier stores that as a template. From then on, every message arriving at that address is compared against the template, and the parser looks for your labelled values in the same place relative to the surrounding text. Those fields then become usable data in any Zap.
That design is the whole story, both the strength and the ceiling. Because the matching is positional and textual rather than semantic, the parser does not know what an invoice number is. It knows that a value sat between the words "Order #" and a line break in the message you trained it on. Give it the same email again and it is fast and free. Give it the same information in a slightly different wrapper and it returns nothing, usually without telling you. Zapier is candid about this in its own documentation: it describes the parser as "just an algorithm", tells you to keep each value on its own line, suggests separating fields with a character such as the pipe, warns you off forwarded messages that carry extra threads and signatures, and recommends creating extra templates when matching fails. Zapier documents a limit of 15 templates, which is the number that decides most cases: one template per sender layout means a shared purchasing or leads mailbox with two dozen senders runs out of room.
There is a second, less discussed cost. Email Parser itself does not carry its own price tag on Zapier's feature page, but it is a trigger, and every parsed email that starts a Zap consumes a task on your Zapier plan. A mailbox receiving a few hundred notifications a month is not free in any practical sense, it is just billed somewhere other than the parser. That matters when you are comparing it against a parser priced per document.
MailParse takes the other approach. You connect the Gmail, Outlook, Microsoft 365, or IMAP mailbox the messages already land in, or forward a sample to a parsing address, and then you name the fields you want rather than pointing at where they happened to sit. It reads the full body and the HTML tables that most business notifications are actually built from, and returns clean Excel, CSV, or JSON. There is no template count to run out of and nothing to re-teach when a sender redesigns their email. Where Zapier wins, and it does win, is when the mail is uniform and the destination is already a Zap: nothing beats a tool that is one click away inside the platform you are automating in. This page is an honest read of both.
What Zapier's parser does well, and where it stops
A fair account of the tool, then the specific failure modes that send people looking for something else.
Templates are positions, not meaning
Zapier remembers that your total sat after the word "Total:" and before a newline. That is precise and fast on a fixed layout. It also means a sender moving a value one line down, or wrapping it in a table cell, produces an empty field rather than a wrong one, and the Zap simply stops firing.
The 15 template ceiling
Zapier documents that a parser mailbox accepts 15 templates. Since the usual fix for a layout that will not match is to add another template, the ceiling arrives faster than people expect. A shared inbox taking leads from a portal, a website form, and a handful of referral partners will hit it.
HTML tables lose their shape
Order confirmations, shipping notices, and lead alerts are usually HTML tables. Template matching works on the text, so a table with five line items flattens into a run of characters with no row boundaries. MailParse parses the table rows, so a message with five line items comes back as five rows.
A separate mailbox to forward to
Zapier parses what arrives at its robot.zapier.com address, so you set up forwarding rules from the mailbox the mail actually reaches. Forwarding adds a hop that can strip formatting, add a quoted header, or get blocked by an outbound spam filter, which Zapier notes as a common cause of messages never arriving.
Every parsed email is a task
The parser is bundled with your Zapier account, but each message it parses triggers a Zap and consumes tasks on your plan. High volume mailboxes are where this shows up. Compare the total against a parser billed per document rather than assuming the parsing itself is free.
Bulk and backfill are not the use case
Zapier parses mail as it arrives, one message at a time, into a workflow. If you need last quarter of order confirmations as a single spreadsheet, point MailParse at the whole folder or label and get one combined file, which is a different job from triggering an automation.
How to set up Email Parser by Zapier
The real sequence, including the step most walkthroughs leave out.
Create the parser mailbox
Sign in to Email Parser, open the Mailboxes page, and create a mailbox. Zapier issues an address ending in robot.zapier.com. Note that the parser interface reports times in Central Time, which matters when you are matching a parsed record against a timestamp elsewhere.
Send one representative email
Forward a real message to that address, ideally an original rather than a forward, since quoted headers and signature blocks are the usual reason a template later fails to match.
Highlight and label the values
In the browser, highlight each value you want and give it a label such as order_number or customer_email. Keeping each value on its own line, or separating fields with a pipe character, is Zapier's own advice and materially improves matching.
Set up forwarding, then use it in a Zap
Add a forwarding rule in Gmail, Outlook, or Microsoft 365 so future mail reaches the parser address, then build a Zap with the new email trigger. If your Zap shows no action available, the usual cause is that the mailbox has not received a parsed message yet, so the fields do not exist to map.
When Zapier is the right answer, and when it is not
Both tools have a lane. Picking wrong is what wastes a week.
One sender, one layout, straight into a Zap
A single automated notification that never changes, feeding an app you already automate through Zapier. Use Email Parser by Zapier. It is bundled with your account, it is a few minutes of setup, and adding another tool buys you nothing.
A shared inbox with many senders
Purchasing, leads, and support inboxes take mail from dozens of sources in dozens of shapes. This is where the 15 template ceiling and the per layout maintenance become the job. Naming fields once and having them found across layouts is the difference.
Order confirmations and line items
When the value you need lives in an HTML table with several rows, positional matching gives you a flattened string. Parsing the table properly gives you one row per line item, which is what a spreadsheet or an inventory system needs.
You need a file, not a workflow
Accountants, analysts, and operations teams often want a clean Excel or CSV file from a folder of email, not a trigger. Zapier has no answer for that shape of request because it is built to start automations, not to export.
MailParse next to Email Parser by Zapier
No template count to run out of
Name the fields you want once. There is no per layout template and no documented ceiling of 15 to plan around.
Reads HTML tables as rows
A confirmation listing five line items returns five rows rather than one flattened block of text.
Files as well as fields
Take Excel, CSV, or JSON, including a whole folder parsed into one spreadsheet, which is a different job from firing a Zap.
Where Zapier wins
It is already inside the platform you automate in, it is bundled with your account, and on a fixed layout it is genuinely quick. If that is your situation, stay with it.
Email Parser by Zapier vs MailParse, side by side
An honest comparison, including the rows where Zapier is the better choice. If what you actually want is a straight replacement rather than an explanation, the Zapier email parser alternative page goes deeper on migration, and the email parser API covers pushing fields as JSON.
| What matters | Email Parser by Zapier | MailParse |
|---|---|---|
| How it finds a value | Matches the position of text you highlighted in one sample message | You name the field you want and it is found across differing layouts |
| Templates per mailbox | Documented ceiling of 15 | No template count; one setup covers many senders |
| HTML tables | Flattened into text, so line items lose their rows | Table rows parsed as rows, one record per line item |
| When a sender redesigns | The template stops matching, usually silently | Named fields keep resolving, no template to re-teach |
| Getting mail in | Forward to a robot.zapier.com address | Connect Gmail, Outlook, Microsoft 365, or IMAP directly, or forward |
| Output | Fields inside a Zap | Excel, CSV, JSON, or an API and webhook payload |
| Backfilling an archive | Not the design; it parses mail as it arrives | Parse a whole folder or label into one combined spreadsheet |
| Where Zapier is better | Bundled with the account, native to Zaps, quickest path on one fixed layout | A separate tool, which is overhead you do not need for a single simple sender |
| What you pay | No separate price published; every parsed email consumes Zap tasks | Priced per parse, independent of your automation platform |
Zapier behavior described here reflects Zapier's published Email Parser documentation as of August 2026, including the robot.zapier.com mailbox address, the stated 15 template limit, the Central Time reporting, and Zapier's own guidance on line breaks, delimiters, forwarded messages, and adding templates when matching fails. Zapier does not publish a separate price for Email Parser on its feature page. Platforms change, so check against your own account before you commit. Zapier and Email Parser by Zapier are trademarks of Zapier Inc. MailParse is not affiliated with Zapier.
Frequently asked questions
How does Email Parser by Zapier work?
It gives you a mailbox at an @robot.zapier.com address. You send one sample email to it, highlight the values you want in the browser, and label each one. Zapier saves that as a template and matches every later message against the same surrounding text, turning the labelled values into fields your Zap can use.
Is Email Parser by Zapier free?
Zapier does not publish a separate price for Email Parser on its feature page, and it comes with a Zapier account. It is not free in practice at volume, because every parsed email triggers a Zap and consumes a task on your plan. A mailbox handling a few hundred messages a month has a real cost, billed as tasks rather than as parsing.
How many templates can Email Parser by Zapier have?
Zapier documents that Email Parser accepts 15 templates. That matters because adding another template is the standard fix when a message will not match, so mailboxes receiving several sender layouts reach the ceiling quickly. One template per layout is the practical planning rule.
Why is my Zapier email parser not parsing?
Almost always the incoming message no longer matches the template. Common causes are a sender changing their layout, a forwarded message carrying quoted headers and a signature block, values wrapped in an HTML table, or a value moving onto a different line. Zapier suggests adding another template or changing the parser engine.
Why does my Zap say no action available for Email Parser?
The parser mailbox has not received and parsed a message yet, so there are no fields for the Zap to offer you. Send a real email to the robot.zapier.com address, confirm it parsed in the Email Parser interface, then reopen the Zap and the fields appear in the trigger step.
Can Email Parser by Zapier read attachments?
Its job is the message body. If the numbers you need live inside a PDF or a spreadsheet attached to the email, parsing the body will not reach them. MailParse is the same in this respect: it parses the body and HTML tables and records attachment filenames, but does not read the data locked inside an attached file, so extract that file with a document tool first.
What is the difference between Zapier email parser and Mailparser?
Email Parser by Zapier is bundled with Zapier and matches text by position from a sample you highlight. Mailparser.io is a paid standalone product with rule based parsing and more control. Zapier's own troubleshooting documentation points people toward Mailparser.io and Parseur when its parser cannot cope, which is a fair summary of the split.
Can I parse email into Google Sheets or Excel with Zapier?
Yes, by pairing the parser trigger with a Google Sheets action in a Zap, which adds a row per parsed email. It works well on a fixed layout. If you want a finished spreadsheet from a folder of existing mail rather than a live automation, that is an export job, and parsing straight to Excel or CSV is the shorter route.
Should I switch away from Email Parser by Zapier?
Not if you have one sender, one stable layout, and a destination you already automate through Zapier. Switch when you are maintaining templates per sender, hitting the 15 template ceiling, losing line items out of HTML tables, or needing a file rather than a workflow trigger.
Parse the email without teaching a template
Forward one message and name the fields you want. No sample to highlight, no template count to plan around, and HTML tables come back as rows.