Zapier Email Parser: Extract Text From Automated Emails
parser.zapier.com
Zapier Email Parser: Extract Text From Automated Emails
1–10 of 86 posts
Re: Zapier Email Parser: Extract Text From Automated Emails
#2Happy to answer any questions! This tool has been in use for many months by some select Zapier users and we decided to finally release it. I definitely want to open source the core extractor bits and document the REST API that powers the Zapier integration.
We have more information on using it in Zapier (the main use case at the moment) here: https://zapier.com/zapbook/updates/308/introducing-zapier-em...
Re: Zapier Email Parser: Extract Text From Automated Emails
#3This is a killer feature for Zapier and i'm really excited. Zapier has been a huge time saver for us at BetterVoice.com.
How many times do you get approached by customers or other vendors about "when are you going to integrate with XYZ" product? If you just integrate ONE time with Zapier, you're immediately connected with over 200 other online services. Then your answer to those customers/vendors can be: "We're integrated with Zapier, so you guys should integrate with them too and you'll get all the other benefits as well". With that answer you accomplish 2 things: 1) you shift the burden to them (2) you can use Zapier as a "testing ground" to see how popular an integration with a particular service is. If one particular Zapier connection starts taking off, then you can consider a direct integration. If only a few people use a particular service connection, then you haven't lost anything.
Re: Zapier Email Parser: Extract Text From Automated Emails
#4We have been using the feature for a while, it has become an integral part of our system. The Zapier team is great and always willing to help out with any issues we have, above and beyond what you would expect.
Re: Zapier Email Parser: Extract Text From Automated Emails
#5Happy to answer any questions! This tool has been in use for many months by some select Zapier users and we decided to finally release it. I definitely want to open source the core extractor bits and document the REST API that powers the Zapier integration. We have more information on using it in Zapier (the main use case at the moment) here: https://zapier.com/zapbook/updates/308/introducing-zapier-em...
Very nice! This looks very useful and easy to use.
How much boilerplate text do you need on either side of a token in order to identify it? Put another way, how much can the template emails vary? If the template format changes is there any sort of notification? Did you use the simplest implementation that could work or is this much more complicate than it looks?
Re: Zapier Email Parser: Extract Text From Automated Emails
#6This seems really useful but I can't think of an example usage. Can someone share an example where this is useful?
Re: Zapier Email Parser: Extract Text From Automated Emails
#7This is incredibly clever. Zapier has already built a fast-expanding platform to relate structured business data, and now is taking steps to grow it even further by structuring unstructured data. SaaS mainstays, watch out.
Re: Zapier Email Parser: Extract Text From Automated Emails
#8I think you've got a typo of "chose" vs "choose" in the step that asks the user to "chose" where the data should be sent.
Re: Zapier Email Parser: Extract Text From Automated Emails
#9I think you've got a typo of "chose" vs "choose" in the step that asks the user to "chose" where the data should be sent.
Ah, thanks! Fix committed and pushing.
Re: Zapier Email Parser: Extract Text From Automated Emails
#10Happy to answer any questions! This tool has been in use for many months by some select Zapier users and we decided to finally release it. I definitely want to open source the core extractor bits and document the REST API that powers the Zapier integration. We have more information on using it in Zapier (the main use case at the moment) here: https://zapier.com/zapbook/updates/308/introducing-zapier-em...
Very nice! This looks very useful and easy to use. How much boilerplate text do you need on either side of a token in order to identify it? Put another way, how much can the template emails vary? If the template format changes is there any sort of notification? Did you use the simplest implementation that could work or is this much more complicate than it looks?
It can actually get pretty complex, the technique we're using is a wacky hacky hodgepodge of Google diff-match-patch that works surprisingly well! If you run into any that don't work, just let us know and we can add it to the test suite and figure it out.