I should have our dev build this report, but don't get me started on that rant :-)
It really would be easier if you just had the creator of the email not BCC you on the subscription fee and just had them cobble together a daily sheet for you. Doesn't need to be anything fancy, just a CSV would do nicely.
Unfortunately we don't have that clever of a parser. We've definitely talked about it but aren't 100% sold on any sort of internal implementation.
We've thought about a "reverse template" where you would mark blocks of text as "variables" across a few examples and we'd parse it out. Not sure if that is feasible though...
Any HN'ers done this before and have ideas or tips?
p.s. Hey Bryan!
It's certainly much simpler than a regex but imposes more structure. We're always open to suggestions, so let me know if you've got any cool ideas on how we can parse smarter.
Happy to answer questions!
For the trigger, choose "GTalk" and "New Message". Specifically, the Zap will trigger whenever you send a message to our always-on bot.
You can pick any action that suites you, see the article for ideas.
We'll automatically perform the action whenever the trigger occurs.
There is a lot of flexibility in the system but that's the 500 foot view.
The title, though, implies a service (or hack) that isn't dependent on any other system -- maybe it might be better titled "Turn Gtalk into a Command Line for the Web using Zapier" or something?