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 gender entries within a gym management system. Specifically, the "Delete" operation under the "Gender" resource allows users to remove a gender record by its unique identifier. This is useful for maintaining accurate and up-to-date gender options in the system, such as when a gender category is deprecated or was created in error.
Practical examples include:
- Cleaning up unused or incorrect gender categories from the system.
- Automating data hygiene workflows where outdated gender entries are removed regularly.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the main data output. |
| ID | The unique identifier of the gender entry to delete. This is required to specify which gender to remove. |
Output
The node outputs JSON data representing the result of the deletion request. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only the essential confirmation or status information is provided.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The node uses the base URL and authentication token configured in the credentials to send HTTP DELETE requests to the endpoint
/settings/genders/{id}.
Troubleshooting
Common issues:
- Invalid or missing ID: The node requires a valid gender ID to delete. Providing an empty or incorrect ID will cause the operation to fail.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network or API endpoint errors: Verify that the base URL is correct and the GymControl API service is reachable.
Error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 Not Found may occur if the specified gender ID does not exist.
- 400 Bad Request could happen if the ID format is invalid.
To resolve these, double-check the input ID, verify API credentials, and confirm the API endpoint availability.
Links and References
- GymControl API documentation (general reference for endpoints and authentication)
- n8n documentation on creating and using API key credentials