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 various resources related to a gym management system. Specifically, for the File resource with the Get operation, it retrieves detailed information about a specific file stored in the GymControl system by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching metadata or content details of a file previously uploaded or managed within GymControl.
- Automating workflows that require accessing file information for reporting, auditing, or further processing.
- Integrating GymControl file data into other systems or dashboards.
For example, you might use this node to get details about a member's uploaded document or an exercise-related media file by specifying its ID.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the main data object. |
| ID | The unique identifier of the file to retrieve from GymControl (required). |
Output
The node outputs JSON data representing the file information retrieved from GymControl. This typically includes all metadata and attributes associated with the file identified by the given ID.
If "Show Complete Response" is enabled, the output will contain the entire API response, which may include additional metadata such as HTTP status, headers, or nested objects beyond the core file data.
The node does not explicitly handle binary data output for files; it focuses on JSON metadata retrieval.
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 node credentials.
- Network access to the GymControl API endpoint is necessary.
Troubleshooting
- Invalid or missing ID: If the provided file ID is incorrect or does not exist, the API will likely return an error or empty response. Verify the ID before running the node.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access file resources.
- Network issues: Connectivity problems to the GymControl API endpoint can cause request failures.
- Unexpected response format: If the API changes or returns unexpected data, enabling "Show Complete Response" can help debug by showing the full raw response.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on creating custom nodes