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 node provides integration with the GymControl system, specifically allowing management of various resources within a GymControl instance. For the Relationship - Delete operation, it enables users to delete a specific relationship record by its ID. This is useful in scenarios where you need to remove associations or links between entities (such as users, roles, or other related data) managed within GymControl.
Practical examples:
- Removing a user-to-role assignment that is no longer valid.
- Deleting a connection between two entities that should no longer be linked in the system.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | If enabled, the node will return the full API response after deletion instead of a simplified output. Options: true or false. |
| ID | The unique identifier of the relationship to delete. This is required to specify which relationship record to remove. |
Output
The node outputs JSON data representing the result of the delete operation. If "Show Complete Response" is set to false, the output will likely be a simplified confirmation of deletion (e.g., success status). If true, the entire API response from GymControl for the delete request is returned, which may include additional metadata or details about the deleted resource.
No binary data output is involved in this operation.
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 credentials.
- The node uses HTTP DELETE requests to the GymControl API endpoint corresponding to relationships.
Troubleshooting
Common issues:
- Invalid or missing ID: The delete operation requires a valid relationship ID; omitting or providing an incorrect ID will cause errors.
- Authentication failures: Ensure the API key and base URL are correctly configured in the credentials.
- Network or connectivity problems: Verify that the GymControl API endpoint is reachable.
Common error messages:
- Unauthorized or 401 errors: Check API key validity and permissions.
- 404 Not Found: The specified relationship ID does not exist.
- 400 Bad Request: The ID format might be invalid or missing.
Resolving these typically involves verifying input parameters, credentials, and network access.
Links and References
- GymControl API documentation (refer to your GymControl provider's official docs for detailed API endpoints and authentication)
- n8n documentation on creating and using custom nodes and credentials