All Collections
Sending emails and documents
Parsing difficulties with different forwardings
Parsing difficulties with different forwardings

Forwarding with different email apps like Gmail, Outlook, Apple Mail, leads to different email content, even if emails look the same

Updated over a week ago

(This article applies only to text-based email parsing.)

The problem

If you created a template from an email forwarded by Gmail, it might not parse an email forwarded by, for example, Outlook. The email's content looks similar, but its underlying structure (the HTML code) is very different and irreconcilable.

The solutions

1 - Try using the AI engine.

Our AI engine parsing capabilities are resistant to forwarding from different email clients and will be able to extract the data irrespective of which email client it was forwarded from. Learn more about using the AI engine.

2 - Send emails directly

Try to send emails directly from your app to Parseur by configuring your app to directly send emails to your * mailbox email address.

3 - Forward from the same provider

If you cannot send emails directly, then try to forward all your emails with the same email application. Emails forwarded by the same application have a consistent structure, and templates created from an email forwarded by application A are more likely to match emails forwarded by application A. Whereas emails forwarded by application B or C have a low probability of matching that template.

The best solution for this is to set up auto-forward rules in your email client. Not only will it make parsing more reliable, but it will also make your workflow closer to 100% automated.

4 - Create a new template for each forwarding email application

If you don't have control over the way emails are forwarded to your Parseur mailbox, then you have no choice but to create a new template for each forwarding email application.

This is quite time-consuming and contrary to what Parseur stands for: saving time for its users. We are acutely aware of that problem and are working to build a new visual parsing system that eases this issue completely. Stay tuned for further updates on the matter.

Did this answer your question?