Withings APIInstall

Overview

This node integrates with the Withings API to retrieve health and activity data related to the "Measure" resource, specifically supporting the "Get Activity" operation. It fetches intraday user activity data such as steps, calories burned, distance, and other fitness metrics recorded by Withings devices.

Common scenarios for this node include:

• Tracking daily physical activity for health monitoring.
• Aggregating fitness data for wellness reports.
• Integrating Withings activity data into broader automation workflows or dashboards.

For example, a user could automate fetching their daily step count and calories burned every morning to log it in a spreadsheet or send a summary notification.

Properties

Output

The node outputs JSON data containing the results from the Withings API call. The structure includes:

• success: Boolean indicating if the API call was successful.
• resource: The resource queried, here always "measure".
• operation: The operation performed, here "getactivity".
• data: The actual activity data returned by the Withings API, which typically includes detailed intraday activity metrics such as steps, calories, distance, and other tracked parameters.

If an error occurs, the output JSON will contain:

• success: false
• error: Error message describing the failure.
• status and errorCode: API error status and code if available.
• resource and operation: Context of the failed request.

The node does not output binary data.

Dependencies

• Requires an OAuth2 API credential configured for Withings API access.
• The node uses Withings API endpoints under https://wbsapi.withings.net.
• Proper scopes and permissions must be granted in the Withings developer account to access activity data.
• Network connectivity to Withings API is required.

Troubleshooting

• Authentication errors: Common messages include unauthorized, invalid token, expired credentials, or permission denied. Resolution steps:
  1. Reconnect or refresh the OAuth2 credential.
  2. Verify that the Withings developer app has the correct scopes enabled.
  3. Ensure the Withings user account is active and linked properly.
• API rate limits or temporary failures: The node implements retries with exponential backoff. If persistent failures occur, check Withings API status or reduce request frequency.
• Invalid date inputs: Ensure that start and end dates are valid ISO timestamps; otherwise, the API may reject the request.
• Empty or unexpected data: Confirm that the user has activity data for the requested period.

Links and References

• Withings API Documentation
• Withings OAuth2 Authentication Guide
• n8n Documentation on OAuth2 Credentials