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 and retrieve data related to a gym management system. Specifically, for the User resource with the Get Many operation, it fetches multiple user records from the GymControl instance. This is useful when you want to list or process many users at once, such as generating reports, syncing user data with other systems, or performing bulk updates.
Practical examples include:
- Retrieving all users to analyze membership trends.
- Exporting user lists for marketing campaigns.
- Synchronizing user data with CRM or email platforms.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled, returns the full API response instead of just the processed user data. |
Output
The node outputs JSON data containing an array of user objects retrieved from the GymControl API. Each user object typically includes fields like name, lastname, role, and other user-specific details as provided by the API.
If "Show Complete Response" is enabled, the output will contain the entire raw response from the API, which may include metadata or additional information beyond just the user list.
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 makes HTTP GET requests to the
/usersendpoint of the GymControl API.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Empty results: Verify that there are users in the GymControl system and that any filters applied (if extended) match existing users.
- Network issues: Confirm that the base URL is reachable from the n8n environment and that no firewall or proxy blocks the request.
- Unexpected response structure: If the API changes, the node might fail to parse user data correctly; enabling "Show Complete Response" can help debug by showing raw API output.
Links and References
- GymControl API Documentation (Assumed link, replace with actual if available)
- n8n HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/