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 Type - Delete operation, it allows users to delete a file type entry from their GymControl instance by specifying its unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of obsolete or unused file types in the GymControl system.
- Integrating with workflows that manage gym data lifecycle, ensuring outdated file types are removed automatically.
- Maintaining data hygiene by programmatically deleting file types without manual intervention.
Example use case:
- A gym manager wants to remove a deprecated file type used for member documents. Using this node, they can automate the deletion process by providing the file type ID, streamlining administrative tasks.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | Boolean option to return the full API response instead of just the main data output. |
| ID | The unique identifier of the file type to delete. This is required to specify which file type to remove. |
Output
The node outputs JSON data representing the response from the GymControl API after attempting to delete the specified file type. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only the essential result data is provided.
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 and API key to be configured in the credentials.
- Network access to the GymControl API endpoint is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent file type ID will likely cause the API to return an error indicating the resource was not found.
- Missing or incorrect API authentication credentials will result in authorization errors.
- Network connectivity issues may prevent the node from reaching the GymControl API.
Error Messages & Resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly set up and has sufficient permissions.
- "Resource not found": Confirm that the file type ID exists in the GymControl system before attempting deletion.
- Timeout or network errors: Check internet connectivity and ensure the GymControl API endpoint is reachable.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes
- General REST API best practices for DELETE operations