This is an n8n community node for integrating with the Withings API. It allows you to connect to your Withings account and access health and fitness data through OAuth2 authentication.

• OAuth2 authentication with Withings API
• Complete integration with Withings API resources:
  • Activity data (getactivity, getsummary, getworkouts)
  • Measurements (getmeas, getactivity, getintradayactivity)
  • Sleep data (get, getsummary)
  • User information (getdevice, getgoals, get)
• Customizable parameters for all API operations
• Proper error handling and response formatting

• n8n (version 1.0.0 or later, tested with 1.104.2)
• Withings developer account and API credentials

Follow these instructions to install this node in your n8n instance:

npm install n8n-nodes-withings

For Docker-based n8n installations, you can use the n8n-docker-custom approach.

1. Create a developer account at Withings Developer
2. Register a new application to get your Client ID and Client Secret
3. Set the callback URL to: https://your-n8n-domain.com/rest/oauth2-credential/callback
4. In n8n, create a new credential of type "Withings OAuth2 API"
5. Enter your Client ID and Client Secret
6. Configure the scopes as needed (default: user.info,user.metrics,user.activity,user.sleepevents)
7. Complete the OAuth2 flow by connecting to your Withings account

The Withings API has some special requirements for OAuth2 authentication:

• The token request requires an additional action=requesttoken parameter
• Authentication for API requests uses Bearer token in the Authorization header
• Token exchange requires specific formatting of the request body
• Access tokens expire after 30 seconds and need to be refreshed frequently
• Signature generation and nonce retrieval are required for enhanced security

This node handles these requirements automatically through a custom authentication implementation. The token refresh is managed automatically with the following mechanisms:

1. Enhanced Security with Signatures: The implementation uses HMAC-SHA256 signatures and nonces for secure authentication:

   • Retrieves a nonce from the Withings API before token requests
   • Generates cryptographic signatures for authentication requests
   • Properly formats request parameters according to Withings requirements
   • Handles scope formatting with proper "user." prefixes
   • Gracefully falls back to standard authentication if signature generation fails

2. Super-Aggressive Token Refresh: Tokens are refreshed 15 seconds before their 30-second expiration (previously 10 seconds)

   • Explicitly specifies refresh_token in the grant type
   • Includes the refresh token in token refresh requests
   • Ensures proper token synchronization between requests
   • Specifies the refresh token key name for precise handling
   • Includes scopes during refresh for complete token state

3. Extreme Token Validation: Multiple validation strategies are employed before each API request:

   • Pre-request validation with up to 7 attempts using different endpoints (increased from 5)
   • Multiple direct token refresh attempts with 5 different fallback strategies (increased from 3)
   • Token state tracking to ensure validity throughout the request lifecycle
   • Cache-busting timestamps with enhanced randomization to prevent stale token issues
   • Comprehensive cache prevention headers with Expires and Pragma directives
   • Unique request IDs for better tracking and cache prevention

4. Advanced Retry Logic: If a token error occurs, the node uses an intelligent retry mechanism with:

   • Enhanced error detection for 25+ token-related error patterns (increased from 20+)
   • Exponential backoff with improved jitter for more effective retries
   • Multiple refresh attempts with increasing delays and randomization
   • Structured approach with 5 different endpoint strategies
   • Fresh request options for each attempt to prevent reference issues
   • Request timeouts to prevent hanging connections
   • Graceful failure with detailed error messages after multiple attempts

These mechanisms work together to ensure reliable API communication even with Withings' short-lived tokens. The implementation is designed to be extremely resilient to token expiration issues, network fluctuations, and API inconsistencies.

The Withings API node provides access to various health and fitness data from your Withings account. Here's how to use it:

1. Add the Withings API node to your workflow
2. Select the Withings OAuth2 API credentials (create them if you haven't already)
3. Choose a resource (Activity, Measure, Sleep, or User)
4. Select an operation for the chosen resource
5. Configure any additional parameters as needed

• Get Activity: Retrieves user activity data
• Get Summary: Gets a summary of user activity
• Get Workouts: Retrieves workout data

• Get Measurements: Retrieves body measurements (weight, height, etc.)
• Get Activity: Gets activity measurements
• Get Intradayactivity: Retrieves detailed intraday activity data

• Get: Retrieves sleep data
• Get Summary: Gets a summary of sleep data

• Get Device: Retrieves information about user devices
• Get Goals: Gets user goals
• Get: Retrieves user information

Most operations support the following parameters:

• Start Date: The start date for data retrieval
• End Date: The end date for data retrieval
• Last Update: Get only data updated after this date
• Offset: Skip this many records

• Measure Type: Select the types of measurements to retrieve (weight, height, blood pressure, etc.)

• Data Fields: Select the types of sleep data to retrieve (heart rate, respiration rate, snoring)

• Withings API Documentation
• n8n Community Nodes Documentation

• 0.6.3: Fixed "Unable to sign without access token" error in sleep summary endpoint with enhanced token validation and special handling for sleep-related requests
• 0.6.2: Fixed "This scope is not allowed" error by ensuring proper scope formatting with "user." prefix in authorization URL
• 0.6.1: Version update for release
• 0.6.0: Implemented signature generation and nonce retrieval for enhanced security based on withings-node-oauth2 library
• 0.5.0: Implemented super-aggressive token handling with extreme validation and enhanced error recovery
• 0.4.9: Implemented hyper-aggressive token handling with extreme validation and synchronization mechanisms
• 0.4.8: Implemented ultra-aggressive token refresh with multiple validation strategies and enhanced error recovery
• 0.4.7: Fixed "Unable to sign without access token" error with enhanced token validation and multi-stage refresh strategy
• 0.4.6: Improved refresh token handling with explicit refresh token grant type and better token synchronization
• 0.4.5: Enhanced token validation and authentication with pre-request validation and improved error handling
• 0.4.4: Fixed "Unable to sign without access token" error with improved token synchronization
• 0.4.3: Enhanced token error detection and improved retry mechanism with smart backoff
• 0.4.2: Improved token refresh handling with exponential backoff retry mechanism
• 0.4.1: Added support for Withings' 30-second token expiration with automatic refresh
• 0.4.0: Fixed empty Access Token URL field by using correct field name (accessTokenUrl)
• 0.3.9: Fixed "Unable to sign without access token" error in sleep summary endpoint
• 0.3.8: Fixed "Unable to sign without access token" error in sleep data endpoint
• 0.3.7: Changed credential type from genericAuth to oAuth2Api to enable Connect button
• 0.3.6: Implemented special Withings OAuth2 requirements with custom token exchange
• 0.3.5: Fixed empty Access Token URL field in credentials
• 0.3.4: Fixed "Unable to sign without access token" error in OAuth2 authentication
• 0.3.3: Made OAuth2 URLs hidden in the credentials UI for cleaner interface
• 0.3.2: Improved compatibility with n8n 1.104.2 for OAuth2 credential fields
• 0.3.1: Fixed Access Token URL field visibility in credentials
• 0.3.0: Fixed authentication issues with OAuth2 implementation
• 0.2.0: Complete implementation of Withings API with all resources and operations
• 0.1.0: Initial release with OAuth2 authentication support

MIT