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
Payment → Get Per User
AI-generatedOverview
The node integrates with the GymControl API to retrieve payment information for a specific user. The "Get Per User" operation fetches all payments associated with a given user ID. This is useful in scenarios where you want to analyze or process payment data related to individual gym members, such as generating reports on member payments, verifying payment status before granting access, or syncing payment records with other systems.
Practical examples:
- Automatically retrieving all payments made by a user to update their membership status.
- Triggering follow-up actions if a user's payment is overdue.
- Aggregating payment data per user for financial reporting.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the processed data. |
| User | The user whose payments are to be retrieved. Can be specified by user ID or selected from a searchable list of users. |
Output
The node outputs JSON data containing the payment details for the specified user. The structure typically includes an array of payment objects with fields such as payment amount, date, status, and related metadata.
If "Show Complete Response" is enabled, the output will include the entire raw response from the GymControl API, which may contain additional metadata or nested information beyond the basic payment details.
No binary data output is indicated.
Dependencies
- Requires connection to the GymControl API via an API key credential.
- The node expects the base URL and API key to be configured in the node credentials.
- Uses HTTP GET requests to fetch user and payment data from GymControl endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Specifying a non-existent user ID will result in empty or error responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication failures usually indicate incorrect or expired API keys; verify and update credentials.
- "User not found" or similar errors suggest the user ID does not exist; confirm the user selection.
- Timeout or network errors require checking internet connectivity and API availability.
Links and References
- GymControl API documentation (refer to official GymControl developer resources for detailed API specs).
- n8n documentation on creating and using custom nodes with API integrations.