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 Addon resource with the Get operation, it retrieves information about a particular addon configured in the GymControl instance. This is useful for scenarios where you want to fetch details about additional features or modules enabled in your gym software setup.
Practical examples include:
- Fetching addon details to display in a dashboard.
- Verifying addon configurations before performing further automated workflows.
- Integrating addon data into reports or notifications.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled, returns the full raw response from the API instead of just the main data. |
Output
The node outputs JSON data representing the requested Addon resource information retrieved from the GymControl API. The structure typically includes all relevant fields describing the addon, such as its ID, name, status, and configuration details.
If the "Show Complete Response" property is set to true, the output will contain the entire API response object, which may include metadata or additional HTTP response details beyond the core addon data.
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 API must be configured in the node credentials.
- The node uses HTTP GET requests to fetch data from endpoints like
/addons.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions to access addon data.
- Resource not found: If the specified addon ID does not exist, the API may return a 404 error. Verify the addon identifier used in the node parameters.
- Incomplete data: If the output seems partial, try enabling "Show Complete Response" to inspect the full API response for clues.
- Network issues: Confirm that the base URL is reachable and there are no firewall or connectivity problems blocking the request.
Links and References
- GymControl API Documentation (hypothetical link)
- n8n documentation on creating custom nodes