It even takes care of deduping contacts for you if the same email address appears in the email.
It can find phone numbers, titles, addresses and attribute them to the correct contact. It can extract contacts and split emails into sections. The SigParser Email Parsing API is a serverless, stateless email parsing API. If an email client like Gmail starts using a new reply header format, we’ll have a fix deployed with days and you won’t have to do anything. As we improve you’ll automatically get any improvements without the need to redeploy any of your code. This is why we expose a simple email parsing API for use with NodeJSĪll of the above is why we suggest using our email parsing service to parse emails from NodeJS. We’ve been labeling our test set for years across many organizations. We use a machine learning algorithm with lots of labeled validation emails. Then there is identifying where the email signature is in the email which is really hard. Even street addresses are massively different by country. Often they’ll only put the city and state but no country. Titles can be incredibly difficult to capture without getting too much wrong information.For example, Mobile vs M: vs Cell vs C: and many others The phone type indicator has lots of variations.Need to attribute the type of phone number (Fax vs Mobile vs Work phones).Phone numbers can have many different formats.Here are some of the major things you’d need to handle. But the more you start working the problem the harder it becomes. Many think they can just use a couple regex expressions and they’ll be done. Parsing email signatures with NodeJS is also difficult. No two email clients seem to produce the same header format and over time the email clients change the way they format headers. If you want to split emails on the headers with NodeJS, that is tough. Why parsing emails is hard Splitting Email Chains Libraries for fetching emails from Gmail, Office 365, Exchange, IMAP….Code Example for parsing emails with SigParser.
0 kommentar(er)
