Live data from Hacker News

Zapier Email Parser: Extract Text From Automated Emails

parser.zapier.com

51–60 of 86 posts

Re: Zapier Email Parser: Extract Text From Automated Emails

#52

Earlier quoted context omitted.

If you want infuriating marketing, try Googling for an integration between two obscure web services. The Zapier "Zapbook" automatically makes a page for each possible combination of the services they hook into, giving useless bullshit like https://zapier.com/zapbook/ducksboard/aim/ (which, by the way, isn't the same as https://zapier.com/zapbook/aim/ducksboard/ either).

Zapier lets you connect apps together in interesting ways, whether or not it really makes sense to. Maybe someone out there will find it useful to be able to manage their dashboards with instant messages.

Indeed, we actually have users doing both of those examples! (None have opted to share their zaps, so the parents' links remain barren.)

Re: Zapier Email Parser: Extract Text From Automated Emails

#53
post #3

This 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 integ…

If you're looking for an open source alternative, please consider my Huginn project, which now has quite an active community. https://github.com/cantino/huginn

Very cool. I have been wishing I had a system like this for a long time.

Re: Zapier Email Parser: Extract Text From Automated Emails

#54
post #15

Can someone share a use case? It seems cool for... something . edit: thanks all, very interesting.

Sure, so whenever someone cancels their Planscope account I send myself an email with their name, email address, LTV, plan, and cancelation reason (this is also stored in my database.) With this, I could simply CC that email to Zapier, they'll yank out all that info and shove it into a Google Spreadsheet, which will let me do certain things that would be a pain to program myself.

Brennan, thanks for sharing your use case. What kind of things would you do with the parsed info in Google spreadsheet?

Re: Zapier Email Parser: Extract Text From Automated Emails

#55
post #35

Earlier quoted context omitted.

I don't understand.. if you send automated emails to yourself in a human-friendly format, why not just use a Google API to push the same data into the spreadsheet at the same time? Zapier may be really cool, but it still seems like you're taking raw data, converting it to human-readable form, then sending that to Zapier to attempt to extract the raw data again. Or am I misunderstanding?

The difference is that you have to do new work every time the destination of the data changes. Using an interface to say "here are the relevant parts" is a lot nicer than having to code it yourself.

Or just push your entire object to google spreadsheet: https://github.com/firmafon/to_google_spreadsheet

Re: Zapier Email Parser: Extract Text From Automated Emails

#58

Can someone share a use case? It seems cool for... something . edit: thanks all, very interesting.

I am playing with it now. I want to have my EZPass (RFID auto tolls) statements sent to my inbox. Right now I get an email with a url, then I have to type a PIN code, just to see my monthly statement. I am too lazy to do it every month, but it would be nice the statements just appeared in my inbox.

Can it fetch data from URL and parse it? The landing page doesn't mention this.

Re: Zapier Email Parser: Extract Text From Automated Emails

#60
Congratulations Bryan for launching it!

We are doing the same at http://mailparser.io and I can confirm that there is a real need for a solution like that. A lot of our existing customers use mailparser.io in combination with Zapier. Those customers can now directly use the parser of Zapier. Which sucks for us but which is surely great for the customer and Zapier ... :-)

One caveat though, a lot of use-cases are not the static "contact form" email where nothing moves except the values. We get a lot of requests for parsing lists, tables etc. Curious how the chosen approach works on this kind of parsing jobs.

Post reply on HN