Microsoft Flow: Expose Public APIs via Custom Connector
In this post we’d like to highlight an article from Premier Developer consultant Megan Meyer’s blog where she walks us through setting up a Custom Connector in Microsoft Flow in order to access data from her FitBit device.
I love fitness trackers. I was excited to get the new Fitbit Alta HR, but some of my eagerness waned when I remembered why I hadn’t used a Fitbit since my old Fitbit One — I hated how it didn’t integrate with any of my other applications I used to track my information. Fitbit does support some integration with partner apps, but just not with any apps that I happen to prefer and use.
Here’s the thing — all of these fitness services provide APIs to interact with their data. All I need to do is write something to make them all talk to each other. I want to achieve a few things; my solution needs to be:
- Easy. I can be pretty lazy when it comes to writing and maintaining software on my own time.
- Flexible and Extensible. I’m not sure exactly what makes the most sense — what data I plan to move from one system to the other, how frequently, etc. I know if I can write something that keeps my options open, I’ll be more likely to continue using it.
- Available. Years ago, I’d hosted a handwritten integrator application on my home computer that synchronized my Nike+ runs with Fitbit. It was unreliable because I did not have an environment meant to be “always on” at my home. I know I need something that’s hosted externally and has the ability to be executing reliably throughout the day to ensure my data is fresh.
Read the rest of Megan’s scenario on her blog here.