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 retrieve feedback data related to users. Specifically, the "Get Per User" operation under the "Feedback" resource fetches feedback entries associated with a particular user. This is useful in scenarios where gym administrators or coaches want to review feedback given by or about individual users, such as athletes or members, to monitor progress, satisfaction, or issues.
Practical examples include:
- Retrieving all feedback for a specific athlete to assess their training experience.
- Gathering user feedback to improve gym services or coaching methods.
- Automating reports on user feedback for management review.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the processed data. |
| User | The target user for whom feedback will be retrieved. Can be specified by ID or selected from a searchable list of users. |
Output
The node outputs JSON data containing the feedback information for the specified user. The structure typically includes an array of feedback entries, each with details such as feedback content, timestamps, and possibly metadata about the feedback source or type.
If "Show Complete Response" is enabled, the output includes the entire raw response from the GymControl API, which may contain additional fields beyond the standard feedback data.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The node configuration must include the base URL of the GymControl instance.
- Network access to the GymControl API endpoint is necessary.
Troubleshooting
Common Issues:
- Invalid or missing API credentials can cause authentication failures.
- Specifying a non-existent user ID will result in no feedback data or an error.
- Network connectivity problems can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "User not found" or empty results suggest checking the user ID or selection method.
- Timeout or connection errors require checking network settings and API availability.
Links and References
- GymControl API documentation (refer to your GymControl provider's official docs)
- n8n documentation on creating and using custom nodes and credentials