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
The node integrates with the GymControl API to manage various gym-related resources. Specifically, for the Payment - Get operation, it retrieves payment information from a GymControl instance. This is useful for scenarios where you want to fetch details about specific payments made in the gym system, such as verifying transactions, auditing payments, or integrating payment data into other workflows like accounting or membership management.
Practical examples:
- Automatically fetching payment details after a member completes a transaction.
- Syncing payment records with external financial software.
- Triggering notifications or reports based on payment status or amounts.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled, returns the full raw response from the GymControl API instead of processed data. It is a boolean toggle (true/false). |
Output
The node outputs JSON data representing the payment information retrieved from the GymControl API. The structure typically includes fields related to the payment such as payment ID, amount, date, payer details, and status. If "Show Complete Response" is enabled, the output will include the entire API response, which may contain additional metadata or nested objects.
The node does not output binary data.
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 requests to communicate with the GymControl service.
Troubleshooting
- Common issues:
- Invalid or missing API key credential can cause authentication failures.
- Incorrect base URL configuration will result in connection errors.
- Requesting a payment ID that does not exist may return empty or error responses.
- Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- Network errors suggest connectivity problems or incorrect API endpoint URLs.
- API errors with status codes (e.g., 404) mean the requested payment resource was not found; check the payment ID input.
Links and References
- GymControl API documentation (refer to official GymControl developer resources for detailed API endpoints and data structures).
- n8n documentation on creating and using custom nodes with API integrations.