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 "File Type" resources, specifically supporting the update operation. It allows users to modify existing file type entries by specifying their ID and updating properties such as name and visibility. This is useful in scenarios where a gym management system needs to maintain or reorganize file types used for categorizing uploaded files, ensuring proper access control and naming conventions.
Practical examples include:
- Renaming a file type from "Membership Card" to "Member ID Card".
- Changing the visibility of a file type to restrict it to authenticated users only.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Whether to return the full API response or just the main data result (true/false). |
| ID | The unique identifier of the file type to update (required). |
| Options | A collection of optional fields to update: |
| - Name | New name for the file type (string). |
| - Visibility | Access level for the file type; options are: Private, Public, Authenticated. |
Output
The node outputs JSON data representing the updated file type resource as returned by the GymControl API. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only the relevant updated data is output.
No binary data output is involved.
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.
- The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Invalid ID error: Occurs if the provided file type ID does not exist. Verify the ID is correct.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Validation errors: If the new name or visibility values do not meet API requirements, the request may fail. Check that the name is a non-empty string and visibility is one of the allowed options.
- Network issues: Confirm connectivity to the GymControl API endpoint and that the base URL is correctly set.
Links and References
- GymControl API documentation (general reference for endpoints and data models)
- n8n HTTP Request node documentation (for understanding how API calls are made)