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 Guest - Delete operation, it allows users to delete a guest record from their GymControl instance by specifying the guest's unique ID.
Common scenarios where this node is beneficial include:
- Automating the removal of guest profiles when they are no longer active or have requested deletion.
- Cleaning up guest data as part of routine maintenance workflows.
- Integrating guest management into broader gym management automation pipelines.
Example use case: Automatically deleting guest records after a membership cancellation event in another system.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the success status. |
| ID | The unique identifier of the guest to be deleted. This is required to specify which guest to remove. |
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 and messages confirming the deletion.
If not enabled, the output likely contains a simplified confirmation indicating whether the deletion was successful.
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 API must be configured in the node credentials.
- The node uses HTTP DELETE requests to the endpoint corresponding to guests.
Troubleshooting
- Missing or invalid ID: The node requires a valid guest ID to perform deletion. Ensure the ID is correctly provided and corresponds to an existing guest.
- Authentication errors: If the API key or base URL is incorrect or missing, the request will fail. Verify that the API credentials are properly set up.
- Permission issues: The API user associated with the credentials must have permission to delete guests.
- API errors: If the guest does not exist or has already been deleted, the API may return an error. Check the full response if "Show Complete Response" is enabled to diagnose.
- Network issues: Connectivity problems can cause request failures; ensure network access to the GymControl API endpoint.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on creating custom nodes