Overview
This node acts as a webhook trigger for GymControl events. It listens for specific event notifications sent by the GymControl system and triggers workflows in n8n when those events occur. This is useful for automating processes based on real-time updates from GymControl, such as member check-ins, class bookings, or equipment usage.
Practical examples include:
- Automatically sending welcome emails when a new member signs up.
- Updating external CRM systems when a member attends a class.
- Triggering alerts or reports based on specific gym activity events.
Properties
| Name | Meaning |
|---|---|
| Event Name or ID | Select an event type from a dynamically loaded list of GymControl webhook event types, or specify an event ID using an expression. |
Output
The node outputs JSON data representing the payload received from the GymControl webhook event. The output structure corresponds directly to the event data sent by GymControl, allowing downstream nodes to process event details such as member info, timestamps, or event-specific metadata.
If the incoming request includes binary data (not indicated here), it would be accessible via the standard n8n binary data handling, but this node primarily deals with JSON webhook payloads.
Dependencies
- Requires an API key credential to authenticate requests to the GymControl API.
- Depends on the GymControl API endpoint to register and manage webhooks.
- Uses a helper function (
gymControlApiRequest) to make authenticated HTTP requests to GymControl. - The node must be configured with a publicly accessible webhook URL to receive events from GymControl.
Troubleshooting
- Unauthorized (403) responses: If the webhook receives requests with invalid or missing signatures, it will reject them with a 403 status. Ensure that the secret stored during webhook creation matches the signature header sent by GymControl.
- Webhook registration failures: Problems creating or deleting webhooks may arise due to incorrect API credentials or network issues. Verify API key validity and connectivity.
- Event not triggering workflows: Confirm that the selected event name or ID matches an available GymControl event type and that the webhook is properly registered.
- Missing or empty event property: The "Event Name or ID" property is required; ensure it is set correctly to avoid webhook creation errors.
Links and References
- n8n Expressions Documentation
- GymControl API documentation (not provided here, but typically needed for deeper integration understanding)