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
This node integrates with the GymControl API to manage gym-related data. Specifically, the "Exercise" resource with the "Get" operation allows users to retrieve detailed information about a specific exercise by its ID. This is useful for scenarios where you want to fetch exercise details to display in reports, synchronize with other fitness apps, or automate workout planning.
For example, you might use this node to:
- Retrieve an exercise's metadata (name, description, muscle groups targeted) to include in a personalized workout plan.
- Fetch exercise details dynamically when building a custom dashboard for gym trainers.
- Automate updates or notifications based on exercise information stored in GymControl.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the main data object. |
| ID | The unique identifier of the exercise to retrieve. This is required for the Get operation. |
Output
The node outputs JSON data representing the exercise details fetched from the GymControl API. The structure typically includes fields such as the exercise name, description, and other relevant attributes defined by the GymControl service.
If "Show Complete Response" is enabled, the output will contain the entire API response, which may include additional metadata beyond the core exercise data.
No binary data output is indicated for this operation.
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 GET requests to fetch exercise data from the endpoint
/exercises/{id}.
Troubleshooting
- Missing or invalid ID: The "ID" property is required. Ensure it is provided and corresponds to a valid exercise in GymControl.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network issues: Check connectivity to the GymControl API URL.
- Unexpected response format: If the API changes, the node might not parse the response correctly. Enabling "Show Complete Response" can help debug by showing raw data.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics