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 retrieve detailed information about logs stored in a GymControl instance. Specifically, the "Log" resource with the "Get" operation allows users to fetch a single log entry by its unique ID. This is useful for scenarios where you want to audit or review specific events or actions recorded in the GymControl system, such as tracking changes, monitoring user activities, or debugging issues.
Practical examples:
- Fetching a particular log entry to investigate an error or unusual activity.
- Retrieving audit trail details for compliance or reporting purposes.
- Accessing specific event data to trigger further automation based on log content.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full raw response from the API instead of just the main data. |
| ID | The unique identifier of the log entry to retrieve. This is required to specify which log to get. |
Output
The node outputs JSON data representing the requested log entry. The structure corresponds to the log object returned by the GymControl API and typically includes fields such as timestamp, user info, action performed, and other relevant metadata describing the log event.
If "Show Complete Response" is enabled, the output will include the entire API response, potentially containing additional metadata beyond the log data itself.
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 instance must be configured in the credentials.
- The node uses HTTP requests to communicate with the GymControl REST API endpoints.
Troubleshooting
- Missing or invalid ID: The "ID" property is required. If omitted or incorrect, the API call will fail. Ensure the correct log ID is provided.
- Authentication errors: If the API key or base URL is misconfigured, the node will fail to authenticate. Verify the API key credential and URL settings.
- API connectivity issues: Network problems or incorrect endpoint URLs can cause request failures. Check network access and credential configuration.
- Unexpected response format: If the API changes or returns errors, the node may not parse the response correctly. Enable "Show Complete Response" to debug the raw output.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on creating custom nodes