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 payments within a gym management system. Specifically, the "Delete" operation under the "Payment" resource allows users to delete a payment record by its ID. This is useful for scenarios where a payment was entered incorrectly or needs to be removed due to cancellation or refund.
Practical examples:
- Automatically removing a payment entry when a membership is canceled.
- Cleaning up test or duplicate payment records during data synchronization.
- Integrating with other systems to maintain accurate financial records by deleting outdated payments.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean flag to determine if the full API response should be returned or just the result. |
| ID | The unique identifier of the payment to delete. |
Output
The node outputs JSON data representing the response from the GymControl API after attempting to delete the specified payment. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only essential information about the deletion result 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 base URL for the GymControl instance must be configured in the node credentials.
- The node uses HTTP DELETE requests to the endpoint corresponding to the payment ID.
Troubleshooting
Common issues:
- Invalid or missing payment ID will cause the API to reject the request.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity problems preventing access to the GymControl API.
Error messages and resolutions:
- "404 Not Found" — The payment ID does not exist. Verify the ID is correct.
- "401 Unauthorized" — Authentication failed. Check that the API key credential is valid and has necessary permissions.
- "400 Bad Request" — The request parameters are invalid. Ensure the ID is properly formatted.
- Timeouts or network errors — Confirm network connectivity and API availability.
Links and References
- GymControl API documentation (general reference for endpoints and authentication)
- n8n documentation on creating and using API key credentials