Overview
This node integrates with the MyFitnessPal API to retrieve user diary entries for a specific date. It is useful for users who want to programmatically access their food and exercise logs from MyFitnessPal, enabling automation of health tracking, data analysis, or integration with other wellness applications.
A practical example would be fetching all diary entries for a given day to analyze calorie intake and exercise activities, which can then be used in custom dashboards or reports.
Properties
| Name | Meaning |
|---|---|
| Date | The date for which to retrieve diary entries. Must be provided in the format YYYY-MM-DD. |
Output
The output is an array of JSON objects representing the diary entries retrieved from MyFitnessPal for the specified date. Each object contains detailed information about the user's logged foods and exercises on that day as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the MyFitnessPal API.
- An API authentication token (API key credential) must be configured in n8n to authorize requests.
- The node makes HTTP GET requests to
https://api.myfitnesspal.com/v2/diarywith the date parameter.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrectly formatted date may result in no data or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired API tokens; reconfigure the API credentials.
- "Date not found" or empty results may mean no diary entries exist for the specified date.
- HTTP request failures should be checked for network issues or API downtime.
Links and References
- MyFitnessPal API Documentation (Note: official public API documentation may be limited)
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)