November 2017: Lists, Tables, Skip, Zapier
We have a truckload of new features and improvements ready for you. It looks like Santa is early this year!
Extract Lists and Tables from emails
This was the single most requested feature since we launched Parseur. You wanted to extract data from lists or tables of varying length with one single template.
We are excited to announce that you can now extract information from lists or tables automatically! And, of course, you can do that very easily in just a few clicks!
Head over to this article to learn more about how to use this awesome feature!
Skip unwanted emails
Sometimes, not all emails you send to Parseur need to be processed. For instance, you may have a forward rule in Gmail to send all your orders from Amazon that ends up sending delivery confirmations and special sales too. You can now "skip" an email by clicking on the eject button in the Document action list.
Once a document is "Skipped", Parseur will not try to process it anymore.
Zapier + Parseur integration now out of beta!
After many months of intensive tests in beta mode, we are happy to announce that our integration with Zapier is now public! Parseur is listed in Zapier's Zapbook.
To celebrate that milestone, we have created dozens of Zap Templates that will help you get started quickly. Zap templates help you integrate Parseur with all the apps that Zapier offers.
You'll find these templates directly in Parseur app:
- open one of your mailbox
- click on the Export section
- click on the Zapier tab
New Parseur API and Documentation
For the most advanced use cases, we are opening Parseur's API to third party apps and developers to create deep integration with our product.
For instance, with our API you can send us documents directly to Parseur via a webhook, which is usually more reliable than sending emails when you have a large volume of data to send. Please refer to the following page for details on how to use Parseur's API.
And much more
Parseur is evolving and improving continually, we deploy updates almost daily. Here is a run down of some other improvements we made recently:
New: "Original Recipient" Extra Field: Extra fields are fields not included in your document content that can be added to your parsed result on top of the custom fields you create . We added a new "OriginalRecepient" extra field. As its name suggest, it will include the email address of the recipient of the email before it got forwarded to Parseur.
New: "View as JSON" result: you now have 2 options to see your parsed result when viewing a document: the standard table option and the JSON option. The JSON option represents the "raw" format of your result. This format is particularly useful to visualize the data extracted from Lists and Tables.
New "Process attachment" field: you can now select whether you want to download email attachments as separate documents. This feature is turned off by default. You can activate it by going to your parser settings and ticking the appropriate box.
Better: GetSwift integration: thanks with the feedback gathered with thousands of delivery emails parsed every month, we have adjusted the GetSwift integration to cover more use cases. Integration is now better at sending formatted dates for GetSwift (you can adjust your date settings in your account). We have also added the possibility to set a default driver fee percentage when you add your GetSwift API Key.
Better: Ready-made field renaming/deleting: if you use one of our ready-made templates (templates managed by us), you can now rename or delete a field.
Better: Under the hood parsing engine improvements: we continually make improvements to our parsing engine to make it smarter at understanding what you need from the emails. The Latest adjustments improve parsing accuracy, resistance to "noise" (reducing occurrences of "new template needed" errors) and performances.
Fixed: Template debugger false positives. In some situation the template debugger would report 100% parsing with a template while your document was showing "New Template Needed". This has now been fixed.
Fixed: Creating a field to extract HTML attribute value. In some situation, if you would create a field to extract an HTML attribute using the "Source (advanced)" view (for example a link href), the parsed result for that field could be empty. This is now fixed and you'll get the proper attribute result in your field.