Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Create an API to link Notion & MyFitnessPal

  • March 16, 2022
  • 3 replies
  • 4080 views
A

Hello,


We started to use Notion at home, for organisation, menus, grocery lists, etc. Wanting to go a bit further, we discovered that it was possible to use Zapier to link some databases to our Notion. Sadly, this option doesn’t seem to be available with MyFitnessPal (yet), an app that allows to track the different nutrients in your daily food consumption, among other things. Basically, what we want to do is twofold : link every ingredient we use to MyFitnessPal database and associate these products to their nutritional value (fat, protein, salt, etc).

My questions are then as follow :
-Do you know if it’s already possible to link Notion & MyFitnessPal ?
-If not, could anyone create an API to do it, or link me to people who can do it ?

We are no coder ourselves, so it’s out of our possibilities on our own.
Thank you in advance

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

3 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • 34082 replies
  • March 16, 2022

Hi @Altarian 

Good question.

 

Here’s the MFP API documentation: https://myfitnesspalapi.com/docs/

App APIs can be used in Zaps with the Webhooks app as an action step: https://zapier.com/apps/webhook/help

If you need help, consider hiring a Zapier Expert: https://zapier.com/experts

⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
A
  • Altarian
  • Author
  • New
  • 1 reply
  • March 17, 2022

Hello,

 

Thank you very much for your quick answer.

From what I can gather, isn’t a webhook just a way of getting notified of a change or an update? By using it, wouldn’t we just get some notification when there’s a change in MFP, without being able to access their database ?

Thank you for your answer, and your patience, as I am quite new to all of this.

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • 34082 replies
  • March 17, 2022

@Altarian

Webhooks in Zaps have 2 functions: triggers & actions

What you’ve described is a Zap webhook trigger a la Catch Hook, in Zap terms.

This would generate a unique webhook URL that can be placed in a origin app to send data payloads when specified events occur.

The origin app would have to support sending webhooks. (This of this as push data from one app to another app)

From what I can see in the MFP API Docs and GSearches, there is no mention of webhooks.

You can reach out to MFP support for clarification whether their app supports webhooks, and if so, how to configure those.

 

Otherwise, you’d have to use the MFP API to pull new data, which is a different approach.

⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
Terms & ConditionsAccessibility statement