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 system to create a new payment record for a user. It is useful in scenarios where you need to automate or streamline the recording of payments made by gym members, such as membership fees, class fees, or product purchases. For example, after a successful transaction on an e-commerce platform or POS system, this node can be used to log the payment details into GymControl automatically.
Properties
| Name | Meaning |
|---|---|
| User | The gym user who made the payment. Can be selected by ID or from a searchable list of users. |
| Amount | The amount of the payment. Must be a number greater than or equal to 1. |
| Payment Date | The date and time when the payment was made. |
| Method | The payment method used. Options: "Card" or "Cash". |
| Category | The category of the payment (e.g., membership, merchandise). |
| Item | The specific item or service the payment is for. |
| Notes | Optional additional notes about the payment. |
| Is Refund | Indicates if the payment is a refund. Boolean value. |
| Refund Reason | Required if the payment is a refund; explains why the refund was issued. |
| Show Complete Response | Node setting to determine whether to output the full API response or just essential data. |
Output
The node outputs JSON data representing the created payment record as returned by the GymControl API. This includes all relevant details of the payment such as user ID, amount, date, method, category, item, notes, refund status, and refund reason if applicable.
If the "Show Complete Response" option is enabled, the entire API response is returned, which may include additional metadata or status information.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a GymControl instance via an API key credential.
- The node uses the GymControl REST API endpoint configured in the credentials.
- Proper API authentication token must be provided in the node credentials.
- Network access to the GymControl API URL is necessary.
Troubleshooting
Common Issues:
- Missing required fields such as user, amount, payment date, or category will cause errors.
- If "Is Refund" is true but no refund reason is provided, the API will reject the request.
- Invalid user IDs or non-existent users will result in API errors.
- Network connectivity issues or incorrect API credentials will prevent successful requests.
Error Messages:
- "User not found" — Verify the user ID or selection.
- "Amount must be at least 1" — Ensure the amount is a positive number.
- "Refund reason required for refunds" — Provide a reason when marking a payment as a refund.
- Authentication errors — Check that the API key credential is valid and has proper permissions.
Resolving these typically involves verifying input parameters, ensuring correct credential setup, and confirming network connectivity.
Links and References
- GymControl API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- Payment Processing Best Practices (general reference)