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 GymControl node integrates with a GymControl instance to manage various gym-related resources. Specifically, the "Workout Execution" resource with the "Get" operation allows users to retrieve details about workout executions from their GymControl system. This is useful for scenarios where you want to fetch data on completed or ongoing workouts, analyze performance, or synchronize workout execution data with other systems such as CRM or analytics platforms.
Practical examples include:
- Automatically retrieving workout execution details after a session ends to update member records.
- Fetching workout execution data to generate reports or dashboards.
- Integrating workout execution information into personalized fitness plans or notifications.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to determine whether to return the full API response or just the main data. |
Output
The node outputs JSON data representing the workout execution(s) retrieved from the GymControl API. The structure typically includes detailed information about the workout execution such as identifiers, timestamps, exercises performed, user details, and status.
If the "Show Complete Response" property is enabled, the output will contain the entire raw response from the API, which may include metadata, pagination info, or additional fields beyond the core workout execution data.
This node does not output binary data.
Dependencies
- Requires an API key credential to authenticate requests against the GymControl API.
- The base URL for the GymControl instance must be configured in the credentials.
- The node uses HTTP GET requests to fetch data from endpoints under the GymControl API.
Troubleshooting
- Authentication errors: Ensure that the API key credential is valid and has sufficient permissions to access workout execution data.
- Invalid resource or operation: Confirm that the selected resource is "Workout Execution" and the operation is "Get".
- Network issues: Verify connectivity to the GymControl API endpoint and that the base URL is correctly set.
- Empty or unexpected responses: Check if the requested workout execution ID exists and that the API returns data for it.
- Enable "Show Complete Response" to debug by inspecting the full API response when troubleshooting data issues.
Links and References
- GymControl API Documentation (example placeholder link)
- n8n documentation on creating custom nodes