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 user data within a gym management system. Specifically, the "User" resource with the "Delete" operation allows you to remove a user from the GymControl platform by their unique ID.
Common scenarios for this node include:
- Automating user account cleanup when a member cancels their subscription.
- Removing test or duplicate user accounts programmatically.
- Integrating with other systems to synchronize user deletions.
For example, after receiving a cancellation event from a payment gateway, you could use this node to delete the corresponding user in GymControl automatically.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean flag to determine whether to return the full API response or just essential data. |
| ID | The unique identifier of the user to be deleted. |
Output
The node outputs JSON data representing the response from the GymControl API after attempting to delete the user. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only relevant confirmation or status information is provided.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The base URL for the API is configured via credentials.
- The node makes HTTP DELETE requests to the endpoint
/users/{id}where{id}is the user ID.
Troubleshooting
- Invalid or missing user ID: Ensure the "ID" property is correctly set and corresponds to an existing user in GymControl.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network issues: Confirm that the base URL is reachable and there are no firewall restrictions.
- API errors: If the API returns an error (e.g., user not found), check the exact message in the complete response if enabled.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n HTTP Request Node documentation for understanding request/response handling.