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 devices associated with users in a gym management system. Specifically, the Delete Device operation allows you to remove a device linked to a particular user. This is useful for scenarios such as revoking access from lost or decommissioned devices, cleaning up outdated device records, or managing user-device associations programmatically.
Practical examples include:
- Automatically deleting a user's device when they leave the gym.
- Removing devices that have been inactive for a certain period.
- Managing device inventory by deleting devices no longer in use.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Whether to return the full API response or just the essential data (true/false). |
| User | The user whose device is targeted for deletion. You can specify the user either by ID or select from a searchable list of users. |
Output
The node outputs JSON data representing the result of the delete operation. If "Show Complete Response" is enabled, the output will contain the full API response from GymControl, which may include status codes, messages, or additional metadata. Otherwise, it returns a simplified confirmation of the deletion.
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 and authentication token must be configured in the node credentials.
- The node uses HTTP requests to communicate with the GymControl REST API endpoints.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a non-existent user ID or device may result in errors or no action.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- 401 Unauthorized: Check that the API key credential is valid and has proper permissions.
- 404 Not Found: The specified user or device does not exist; verify the IDs used.
- 400 Bad Request: Input parameters might be malformed or incomplete; ensure required fields are set correctly.
Resolving these typically involves verifying credentials, confirming user/device existence, and ensuring correct input parameters.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication