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, for the "Exercise" resource and the "Delete" operation, it allows users to delete an existing exercise by its unique identifier. This is useful in scenarios where exercises are no longer relevant or need to be removed from the system to keep the workout database clean and up-to-date.
Practical examples:
- Removing outdated or incorrect exercise entries from a gym's exercise catalog.
- Automating cleanup of exercises that are deprecated or replaced.
- Managing exercise lifecycle within automated workflows for gym management.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to determine if the full API response should be returned or just the result. |
| ID | The unique identifier of the exercise to delete. This is required to specify which exercise to remove. |
Output
The output JSON contains the response from the GymControl API after attempting to delete the specified exercise. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only essential confirmation data is provided. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The base URL for the GymControl instance must be configured in the node credentials.
- The node uses HTTP DELETE requests to the endpoint
/exercises/{id}to perform deletions.
Troubleshooting
Common issues:
- Invalid or missing exercise ID will cause the deletion to fail.
- Authentication errors if the API key or base URL is incorrect or expired.
- Network connectivity problems preventing access to the GymControl API.
Error messages:
- "404 Not Found": The specified exercise ID does not exist. Verify the ID is correct.
- "401 Unauthorized": Authentication failed. Check the API key and credentials configuration.
- "400 Bad Request": The request parameters may be malformed. Ensure the ID is properly formatted.
Resolutions:
- Double-check the exercise ID input.
- Confirm API credentials and permissions.
- Test connectivity to the GymControl API endpoint outside n8n to isolate network issues.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes