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 Social resource with the Get operation, it fetches social-related information from the GymControl instance. This can be useful for scenarios where you want to automate the retrieval of social data such as social media links or social engagement details associated with the gym or its members.
Practical examples include:
- Automatically fetching and displaying social profiles linked to gym users.
- Integrating social data into marketing workflows.
- Monitoring social engagement metrics within automated reports.
Properties
| Name | Meaning |
|---|---|
| Show Complete Response | When enabled (true), the node returns the full raw response from the GymControl API. Otherwise, it returns a simplified or processed subset of the data. |
Output
The node outputs JSON data representing the requested social information from the GymControl API. The structure of the json output field corresponds directly to the API's response for the Social resource.
If "Show Complete Response" is enabled, the entire API response is returned, which may include metadata, pagination info, and all fields provided by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating requests to the GymControl API.
- The base URL for the API is configured via credentials.
- The node uses HTTP GET requests to fetch data from endpoints under the
/socialspath (implied by the resource name). - No additional external dependencies are required beyond the GymControl API access.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Network issues: Verify that the base URL is correct and accessible from the n8n environment.
- Empty or unexpected responses: Check if the Social resource actually contains data in the GymControl instance.
- Incorrect property usage: If "Show Complete Response" is not enabled, some expected fields might be missing because the node filters or simplifies the response.
Common error messages would likely relate to HTTP status codes such as 401 Unauthorized (invalid API key) or 404 Not Found (incorrect endpoint/resource).
Links and References
- GymControl API Documentation (hypothetical link; replace with actual if available)
- n8n documentation on creating custom nodes