See also:
Limitations of the Email Parser Web App
How to run the Windows app in the cloud
Both apps work and look the same way. All the general concepts like the workflow diagram, the fields, parsing rules, etc. apply to both. But there are specific features that only work on either the Web app or the Windows app.
The Windows app is more powerful as it does not have restrictions when operating with files on your computer. It supports scripting in multiple languages (including C#, PowerShell, and JavaScript) and calling other programs when an email is parsed. Another important benefit of the Windows app is that there is no limit on the number of email accounts or emails you can process. On the contrary, the Windows app requires a computer running all day long to parse your emails as they are received.
The most notable benefit of the Web app is that it is easier to manage as there is no computer to keep running. It also has a built-in email inbox (an email address ending in @inbox.emailparser.com), so you do not need to set up one. The Web app supports running JavaScript both as a way to filter incoming emails and as a full scripting action in your workflow, and it also supports running AWS Lambda functions. The most notable drawback is that it cannot operate with files or programs on your computer. The number of emails per month is limited to 5,000. Additionally, the number of AI-assisted field captures is limited to 500 per month, although this limit is lifted if you provide your own OpenAI API key.
| Windows App | Web App | |
|
Maximum number of processed emails
| Unlimited | 5000 per month |
|
Maximum number of email accounts supported
| Unlimited | 10 |
|
Maximum number of AI-assisted field captures per month
| Unlimited (own OpenAI API key required) | 500 per month (unlimited with own OpenAI API key) |
Most email account types, methods of parsing and actions are supported on both versions. But there are some of them only supported on either the Windows app or the Web app: