Actions91
- Account Setting Actions
- Addon Actions
- Ceiling Actions
- Company Info Actions
- Device Actions
- Exercise Actions
- Feedback Actions
- File Actions
- File Type Actions
- Gender Actions
- Guest Actions
- License Actions
- Log Actions
- Payment Actions
- Permission Actions
- Relationship Actions
- Role Actions
- Service Actions
- Service Price Actions
- Social Actions
- Topic Actions
- User Actions
- Workout Execution Actions
- Worksheet Actions
Overview
The node integrates with the GymControl API to update device information associated with a specific user. It allows users to modify device details by specifying the user and providing optional authentication tokens if needed. This node is useful in scenarios where gym management systems need to keep device records up-to-date, such as updating a member's connected fitness device or managing device access.
Practical examples include:
- Updating a user's registered fitness tracker or smart device.
- Changing device settings or tokens linked to a user account.
- Managing device inventory or access control within a gym environment.
Properties
| Name | Meaning |
|---|---|
| User | The user associated with the device to update. Can be selected by ID or from a searchable list of users. |
| Options → Token | An optional token string used for additional authentication or device-specific authorization. |
| Show Complete Response | Boolean flag to determine whether to output the full API response or just essential data. |
Output
The node outputs JSON data representing the updated device information returned by the GymControl API. If "Show Complete Response" is enabled, the entire API response is provided; otherwise, only key fields relevant to the device update are included.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The base URL for the API is configured via credentials.
- The node uses HTTP requests to communicate with the GymControl service endpoints.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly set and has sufficient permissions.
- User not found: Verify that the user ID or selected user exists in the GymControl system.
- Invalid token: If using the optional token property, confirm it is valid and correctly formatted.
- API connectivity issues: Check network access to the GymControl API endpoint and verify the base URL configuration.
- Incomplete responses: Toggle the "Show Complete Response" option to debug and see full API replies.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for understanding request handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/