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 "Service" resource with the "Delete" operation allows users to delete a service entry from their GymControl instance by specifying its ID. This is useful for maintaining an up-to-date list of services offered by a gym, removing outdated or incorrect entries.
Practical examples:
- Removing a discontinued fitness class or personal training service.
- Cleaning up test or duplicate service entries in the system.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | If enabled, the node will return the full API response after deletion; otherwise, minimal output. |
| ID | The unique identifier of the service to be deleted. This is required to specify which service to remove. |
Output
The node outputs JSON data representing the response from the GymControl API after attempting to delete the specified service. If "Show Complete Response" is enabled, this output includes the entire API response object, which may contain status information or details about the deletion result.
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The base URL for the GymControl API must be configured in the node credentials.
- The node sends HTTP DELETE requests to the endpoint corresponding to the service resource.
Troubleshooting
Common issues:
- Providing an invalid or non-existent service ID will likely cause the API to return an error.
- Missing or incorrect API authentication credentials will prevent successful communication with the GymControl API.
- Network connectivity problems can cause request failures.
Error messages and resolutions:
- Unauthorized or 401 errors: Check that the API key credential is correctly set and has sufficient permissions.
- 404 Not Found: Verify that the service ID exists and is correct.
- 400 Bad Request: Ensure the ID parameter is provided and properly formatted.
- Timeouts or network errors: Confirm network access to the GymControl API endpoint.
Links and References
- GymControl API documentation (refer to your GymControl account or developer portal for official API docs)
- n8n HTTP Request node documentation for understanding how API calls are made within n8n workflows