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 retrieve various data related to gym management. Specifically, for the "Account Setting" resource and the "Get" operation, it fetches the current account settings from a GymControl instance. This is useful for scenarios where you want to programmatically access configuration details of your gym's account, such as preferences or global settings.
Practical examples include:
- Automatically syncing account settings into another system for backup or auditing.
- Triggering workflows based on specific account configurations.
- Monitoring changes in account settings over time.
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 account settings retrieved from the GymControl API. The structure corresponds directly to the API's response for account settings, which typically includes configuration parameters relevant to the gym's account.
If "Show Complete Response" is enabled, the output will contain the entire API response object, including metadata and any additional fields beyond the core account settings.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the GymControl API.
- The node expects the base URL of the GymControl instance to be provided via credentials.
- Network connectivity to the GymControl API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect base URL in credentials can lead to connection errors.
- API rate limits or downtime may result in request failures.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Network errors suggest connectivity problems; check internet access and API endpoint availability.
- Unexpected response formats may occur if the API version changes; ensure compatibility.
Links and References
- GymControl API Documentation (example placeholder link)
- n8n documentation on creating custom nodes