GymControl icon

GymControl

Handle your GymControl instance

Actions91

Overview

This node integrates with the GymControl API to manage various gym-related resources. Specifically, for the "Topic" resource and the "Remove User From Topic" operation, it allows users to remove a user from a notification topic within the GymControl system. This is useful in scenarios where you want to unsubscribe or detach a user from receiving notifications related to a specific topic.

Practical examples include:

  • Removing a user from a promotional or informational notification group.
  • Managing user subscriptions dynamically based on their preferences or status changes.
  • Automating user management workflows in gym communication channels.

Properties

Name Meaning
Show Complete Response When enabled, the node returns the full response from the GymControl API instead of just the main data payload.
ID The unique identifier of the topic from which the user will be removed.

Output

The node outputs JSON data representing the response from the GymControl API after attempting to remove the user from the specified topic. If "Show Complete Response" is enabled, the entire API response is returned; otherwise, only the essential data is provided.

There is no indication that this node outputs 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 node credentials.
  • The node makes HTTP requests to endpoints under the GymControl API, specifically targeting notification topics.

Troubleshooting

  • Common Issues:

    • Invalid or missing topic ID: Ensure the "ID" property is correctly set to a valid topic identifier.
    • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
    • Network or connectivity issues: Confirm that the GymControl API endpoint is reachable from the n8n environment.
  • Error Messages:

    • Authorization failures typically indicate invalid or expired API keys.
    • Not found errors suggest the topic ID does not exist or the user is not subscribed to the topic.
    • Validation errors may occur if required parameters are missing or malformed.

To resolve these, double-check input parameters, credentials, and network access.

Links and References

Discussion