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 and retrieve data related to a gym management system. Specifically, for the Guest - Get operation, it fetches information about guests registered in the GymControl system. This can be useful for automating workflows that require guest details, such as sending notifications, generating reports, or syncing guest data with other systems.
Practical examples include:
- Automatically retrieving guest profiles when a new workout session is scheduled.
- Fetching guest information to personalize communication or marketing campaigns.
- Integrating guest data into CRM or membership management tools.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | If enabled (true), the node returns the full raw response from the GymControl API; otherwise, it returns only the processed relevant data. |
Output
The node outputs JSON data representing the guest information retrieved from the GymControl API. The structure typically includes guest attributes such as name, ID, contact details, and any other fields provided by the API for guests.
If "Show Complete Response" is enabled, the output will contain the entire API response, which may include metadata and additional fields beyond the core guest 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 instance must be configured in the credentials.
- The node uses HTTP requests to communicate with the GymControl REST API endpoints.
Troubleshooting
- Authentication errors: Ensure the API key and base URL are correctly set in the credentials. Invalid or missing credentials will cause authorization failures.
- Resource not found or empty responses: Verify that the guest ID or query parameters (if any) are correct and that the guest exists in the GymControl system.
- Network issues: Check connectivity to the GymControl API endpoint and firewall settings.
- 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 the raw API output.
Links and References
- GymControl API Documentation (Assumed URL, replace with actual if known)
- n8n Documentation on Creating Custom Nodes