Capture contacts from emails with SigParser

The average office worker receives 121 emails per day. In most of those emails are going to be signatures. So how many of those contacts and their details ever make it into your CRM system or marketing systems? From our survey’s of users and business leaders while building Salesmino, we learned only about 20% on average. But a bigger problem is the contact data in the CRM and marketing systems get out of date.

We recently released our signature parsing code for emails as a stand-alone API and integration which allows you to capture all your business emails, parse them and load them into your daily systems. This means contact data isn’t slipping thru the cracks.

How it Works

Notice the signature at the bottom of the email. That’s a lot of data you want to capture. A year from now, someone else in the company might need the phone number for the contact or maybe marketing wants to follow this person on Twitter or you could setup a rule to auto follow on LinkedIn.

So our code reads the email and tags each component with what we think it is. If it looks like a cell phone, we’ll tag that.

Notice how we label each component. Although not called out, LinkedIn and Twitter URLs will also be captured.

So how do I use this?

The easiest way is to use a service like Zapier or After you create an account as you will be provided with an API key. You’ll need to use this API key with the following services.

In Zapier, you could join our integration beta and then setup a flow like this.

Whenever an important email arrives, Zapier will invoke the Parse Signature action. That action will then output all the signature components.

I then want to save the contact data to a Google Sheet. The output could be any of their hundreds of providers but in this case I add it to a Google Sheet by finding the row if it already exists and updating it or creating a new row.

You might want to add a filter after the Parse Signature action to ensure you get a title or phone number because sometimes a complete signature isn’t provided and you might want to ignore those cases. allows for more complex control flows than a tool like Zapier.

In the screenshot you can see how a workflow was setup to feed data from Gmail into SigParser.

You could setup branching logic depending on how much signature data we captured. For example, if we didn’t get a title or phone number, you might not want to save any data. Or if we found a Twitter URL, you could feed that to the Twitter provider “Follow person”.


Start using our integromat integration by visiting this page and adding our app as a provider to your integromat account.

integromat is similar to in that it also supports connecting and have branching logic.

Direct API Call

Finally, you could call the API directly from your code C#, JavaScript, Python or whatever language you use via our REST API.

You can view the detailed spec on our API at our Swagger portal.

To test email formats, you can use the portal as well. Click the “Authorize” button on the far right and add your API key. Then click the POST /api/Email method. Then click “Try it out” to add fake request.