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 system to retrieve multiple workout execution records. Specifically, the "Get Many" operation under the "Workout Execution" resource fetches a list of executions related to workouts. This is useful for scenarios where you want to analyze or process multiple workout sessions, such as generating reports on user activity, tracking progress over time, or syncing workout data with other systems.
Practical examples include:
- Fetching all workout executions for a specific workout to analyze performance trends.
- Retrieving recent workout sessions to update dashboards or send notifications.
- Integrating workout execution data into fitness apps or CRM systems for enhanced user insights.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the processed data. |
| ID | The unique identifier of a specific execution (required for single get or delete operations). |
| Workout | Locator for the workout to filter executions by; can be specified by ID or selected from a list. |
Note: For the "Get Many" operation on "Workout Execution", the key input is the "Workout" property which allows selecting the workout whose executions are to be retrieved.
Output
The node outputs JSON data representing the workout executions retrieved from the GymControl API. The structure typically includes an array of execution objects, each containing details about individual workout sessions such as timestamps, user info, and performance metrics.
If the "Show Complete Response" property is enabled, the output will include the entire raw API response, which may contain additional metadata or nested information beyond the core execution data.
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 GET requests to fetch data from endpoints like
/worksheet/{id}to retrieve workouts and their executions. - No other external dependencies or environment variables are explicitly required.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect workout ID may result in empty results or errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Not Found" errors suggest the specified workout or execution ID does not exist; double-check IDs.
- Timeout or connection errors require checking network access and API availability.
Resolving these usually involves verifying credentials, ensuring correct input parameters, and confirming network connectivity.
Links and References
- GymControl API Documentation (Assumed link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices