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 "Get Many" operation for the "Log" resource in this GymControl node retrieves multiple log entries from a GymControl instance. This operation is useful for scenarios where you want to fetch and analyze logs related to gym activities, system events, or user actions within the GymControl platform. For example, a gym manager might use this node to monitor recent activity logs to track member check-ins or equipment usage.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled (true), the node returns the full API response including metadata; otherwise, it returns only the relevant data portion. |
Output
The output of this operation is JSON data representing multiple log entries retrieved from the GymControl API. The structure typically includes an array of log objects with details such as timestamps, event types, user information, and other relevant log data.
If the "Show Complete Response" property is set to true, the output will include the entire API response, which may contain additional metadata like pagination info or status codes.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The node uses the base URL and authentication token provided by the user's GymControl credentials.
- No additional external dependencies are required beyond access to the GymControl API.
Troubleshooting
- Authentication Errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and has sufficient permissions.
- Empty or Missing Data: Ensure that there are logs available in the GymControl system matching the query parameters. Also, check network connectivity to the GymControl API.
- API Rate Limits: Frequent requests might hit API rate limits; consider adding delays or handling retries.
- Unexpected Response Structure: If the "Show Complete Response" option is disabled but the output seems incomplete, try enabling it to debug the full API response.
Links and References
- GymControl API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes