I thought I'd use this week's Tip and Tricks series to show a practical example of how I am using Azure. I've started running outdoors and would like to extract several links that my app generates via email and send them to my OneDrive account automatically vs doing it manually after each run. I'm also concerned that the app that generates my data may be abandoned one day. In order to secure my data, I used a combination of Zappier.com and Azure to solve my problem and over the course of this week, we'll cover the following sections needed in order to implement this:
Once a run is complete, the app that I use (Runmeter) generates an email with a link to the run data (GPX, CSV, KML File) in the following format:
Finished Run: Oct 19, 2017 at 8:46:32 PM Route: New Route Explorer Link: http://runmeter.com/xxx/Run-20171019-2045 Import Link: http://share.abvio.com/xxx/Runmeter-Run-20171019-2045.kml Run Time: 1:04 Stopped Time: 0:00 Distance: 0.00 miles Average: 0:00 /mile Fastest Pace: 0:00 /mile Calories: 4 GPX Link: http://share.abvio.com/xxx/Runmeter-Run-20171019-2045.gpx CSV Link: http://share.abvio.com/xxx/Runmeter-Run-20171019-2045.csv
The pieces of data that we'd like to extract are the
csv URLs and the last piece of the Explorer Link URL. After we have the URLs, then we are going to download them automatically into a OneDrive folder.
I decided to use parser.zappier.com to parse my email data. I did so for a couple of reason:
So fire up parser.zappier.com and create a mailbox. You'll need to send an email to it as it will be your starting template. Once you've sent an email, then select the pieces of data that you want to use and give them a name. In the example below, I've already selected 4 pieces of data and show how to create a new one.
Now that you have your mailbox created and the parser engine knows what data to extract, we can connect the app to The Zappier Editor. But first let's review the pieces of data that we wanted to extract and why.