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 types within a GymControl instance. Specifically, the "Create" operation under the "File Type" resource allows users to create new file type entries by specifying their name and visibility settings.
Common scenarios for this node include automating the management of file types used in a gym management system, such as adding new categories for documents or media files that gym staff or members might upload or access. For example, a gym administrator could use this node to programmatically add a new file type called "Workout Plans" with public visibility so that all authenticated users can view workout plan documents.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the file type to be created. This is a required string input. |
| Visibility | The visibility level of the file type. Options are: Private, Public, Authenticated. |
Output
The node outputs JSON data representing the response from the GymControl API after creating the file type. This typically includes details about the newly created file type such as its ID, name, visibility, and any other metadata returned by the API.
If the "Show Complete Response" setting is enabled, the node will output the full API response; otherwise, it may output a simplified or partial version focusing on the main created entity data.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The node expects the base URL of the GymControl instance to be configured in the credentials.
- HTTP requests are made to the GymControl API endpoints to perform the creation of file types.
Troubleshooting
- Authentication errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify that the API key credential is correctly set up and has sufficient permissions.
- Validation errors: Missing required properties like "Name" or invalid values for "Visibility" will cause the API to reject the request. Ensure all required fields are provided and valid.
- API connectivity issues: Network problems or incorrect URLs can cause request failures. Confirm that the GymControl API endpoint is reachable from the n8n environment.
- Unexpected API responses: If the API changes or returns unexpected data, the node's output may not be as expected. Check the GymControl API documentation for updates.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes