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
The node integrates with the GymControl API to manage various gym-related resources. Specifically, for the Topic - Get operation, it retrieves information about notification topics configured in a GymControl instance. This is useful for workflows that need to fetch and process notification topics, such as automating alerts, managing communication channels, or syncing topic data with other systems.
Practical examples include:
- Automatically fetching all notification topics to update a CRM or messaging platform.
- Triggering actions based on specific topic details retrieved from GymControl.
- Auditing or reporting on notification topics used within the gym management system.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled, returns the full raw response from the GymControl API instead of processed data. |
Output
The node outputs JSON data representing the requested Topic(s) information from the GymControl API. The structure typically includes fields describing each notification topic, such as its name and identifier.
If "Show Complete Response" is enabled, the output contains the entire API response object, which may include additional metadata beyond just the topic list.
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 provided via credentials.
- HTTP requests are made to endpoints like
/notification/topicsto fetch topic data.
Troubleshooting
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access notification topics.
- Network issues: Verify the base URL is correct and accessible from the n8n environment.
- Empty results: Confirm that notification topics exist in the GymControl instance; otherwise, the returned list will be empty.
- Unexpected response format: If the API changes, the node might fail to parse the response correctly. Enabling "Show Complete Response" can help debug by showing raw data.
Links and References
- GymControl API Documentation (general) (Assumed typical location, replace with actual if known)
- n8n documentation on creating custom nodes