Email Parser

Extract data from incoming emails and automate your workflow


How to create a contact under Google Contacts from Email Parser

May 9, 2019



Email Parser is often used to feed a CRM with contacts captured from the received emails. The emails can be, for instance, form submissions from your website or people requesting information sending you a message. For small businesses and individuals, a good way to keep a list of customers or leads is just using the contacts of your Google account. In this blog post we will briefly explain how to add contacts to Google Contacts from Email Parser.

Email Parser can communicate directly with many online services such as Google Sheets, Databases, Web APIs etc. but can also use Zapier to send data to a vast array of other services such as Salesforce, Facebook, Slack etc. We will use Zapier in this case to intermediate between your Google account and Email Parser.

The left panel configuration to do this is shown below. It is a brief example, you may have other fields such as address, company name etc. But just for showing how it is done we are using the name, phone number and email address only:





The steps for settings this up are:

  1. Download and Install Email Parser.
  2. Add your email account and then create a Parser that captures all the contact data from your incoming emails (name, address, etc)
  3. Once Email Parser is correctly capturing all the data from the emails, create a Zapier action. To get the webhook URL you have to follow the steps shown in this page.
  4. Configure under Zapier which Email Parser fields correspond to which Google Contacts fields.




How to merge multiple field values into one

February 26, 2019


Email Parser processes the emails running items (Email sources, Parsers and Actions) one after another, in a sequential way. In each step, a set of fields are created based on the results of the previous steps. For instance, an Email Source creates the field Subject and then a Parser can use this field to capture, let’s say, an invoice number.

There are fields, like the To, CC and BCC that can contain multiple values. For example, the following email contains two values in the CC field:


Multiple field values is something that also happens as a result of parsing, for instance, the body of an email:



Having the values separated, like in an spreadsheet, is what makes most sense in the majority of the cases. But it could happen that you need them merged into a single text value. In order to get this you have to run a small script like the following:

read more …

Email Parser 5.2

February 15, 2019

The changes in this release are:

  • [New] Email sources, Parsers and Actions can now be grouped in tabs at the left panel. This is specially useful if you have a very complex set up with a large amount of items
  • [New] Items in the left panel can now be moved with the mouse (drag and drop). Easier and faster than clicking to the button “up” or “down” multiple times.
  • [New] Support for Zapier.
  • [New] Support for IFTTT.
  • [New] Capturing HTML tags from the email body with XPATH expressions.
  • [New] Capturing HTML tags from the email body with CSS selectors.
  • [New] Added many key shortcuts, mostly the Enter and Esc keys in many panels and lists
  • [New] Added a context menu to the Output tab and the list of emails.
  • [Fix] The email sources that take files from a folder in your computer now are named using the name of the folder instead of requiring a ‘fake’ email address.
  • [Fix] New payment gateway for EmailParser online: Paddle.
  • [Fix] Completely reworked license key panel at Settings->License. Much easier to understand and less nonsense.
  • [Fix] The action that saves the email attachments to a folder now creates a field named SavedAttachmentPath for every saved file. Previously it was named SavedAttachment which was confusing with the actual contents of the attachments.
  • [Fix] Many other small bug fixes and tweaks.


How to correct the email date/time to the required time zone

January 8, 2019


Email Parser automatically uses your local time (as set in Windows) to give a value to the fields DateTimeSent and DateTimeProcessed. But you may need to have these times adjusted to UTC+0 time or another time zone. For this you need to use a small script:

read more …

Email Parser 5.1

November 5, 2018
  • [New feature] Email list under the email source now shows a small ‘v’ icon when an email is already processed. There is no longer needed to open emails one by one to see if they are processed or not.
  • [Fix] The panel where an action is edited sometimes didn’t update accordingly when other actions were changed on a different tab. This is now fixed
  • [Fix] Some processed emails didn’t show as processed under the email list. Sometimes refreshing the view fixed this but now it always work and the update happens automatically.
  • [Fix] Many Email Parser online fixes.
  • [Fix] Other minor bug fixes and memory handling issues


Email Parser 5.0

October 19, 2018
  • [New feature] Faster email processing thanks to the automatic email retrieval. There is no longer needed to set a periodic time value to check emails under preferences. Emails are automatically processed as they are received at the email server.
  • [New feature] The “Email History” or “Processed Emails” window is no longer available. Instead of that you can see all your emails in your account (as any email client, such as Outlook) . If the selected emails happens to be already processed more information is available.
  • [New feature] New actions to integrate with online APIs: HTTP action and Zapier integration
  • [New feature] The email source type that allowed you to just retrieve email files (.eml and .msg formats) from a normal folder in your computer now also allows you to accept any type of document file. It will automatically create a blank email and attach that document as if it was sent in an email.
  • [New feature] A different way to parse attached file. Email Parser now reads the attachment contents when the user creates a field of type “Attachment reader”. This allows to fine tune the way conversion to plain text is done and also speed up email processing to those users who do not care about attachments as they are not read by default.
  • [Fix] Much faster run mode change.


How to save email attachments and body text to a different folder for each email

September 2, 2018

Email Parser is commonly used to capture text from incoming emails and update databases, spreadsheets etc. but another very common use case is to use it as an email archiving tool. We have recently received the following question regarding the latter:


I’m considering using Email Parser to catch mails from an Office 365 account, and save all the attachments to a folder.

I don’t want the attachments to be saved in one big folder. Instead, I need one sub-folder to be created per email received. Name of the subfolder can be a timestamp or ID. Or name of subject but there is a risk of same names.

I also want the body of each mail to be saved in the corresponding sub-folder as an html file or even better as a .pdf file.


(We have properly anonymized and slightly changed the text for privacy)


A configuration that does so looks as following:

read more …

Creating a field with a number to use it as index

August 10, 2018


Recently, a user has posted an interesting question in this website forum:


I’m writing to a text file.
Here’s my “Text to insert”:

I’d like some way to increment the “1” with each successive line I extract from the e-mail….

I’ve been trying to create a static field above, and increment it.. tried a script & do it in C#…
and Thanks,

In this case, the user wanted an index value to write to a text file but it may also happen that you need an index value to insert to a database table. If doing so note that database tables can generate their own index when the SQL INSERT command is sent. But you can also provide them your own index value manually if you want to.


For example, if we retrieve the following fields from an incoming email:


read more …

Email Parser 4.8

May 28, 2018

This new version contains only small bug fixes and performance improvements over the recent 4.7 release. As usual, you can download it from the downloads section.

  • [Fix] Gmail labels, IMAP and Exchange folders browse in the email source settings do not timeout so quickly. Good for slow connections or long lists of labels/folders
  • [Fix] Exchange version 2007 is now actually supported.
  • [Fix] Improved fault tolerance of the changing running mode window when connection errors happens
  • [Fix] Small performance improvements when saving large settings files
  • [Fix] Added more detailed info of very old emails information in the Processed emails tab. See Limitations of the size of the internal database
  • [Fix] Many minor bug fixes


New example: How to parse a table in an email and export to Excel

April 26, 2018

We have added to the examples section a step-by-step guide on how to capture table data and export it to an Excel file using the capture method “Capture HTML tag”. This capture method is a new feature added in the latest version of Email Parser (4.7).