I cannot install FITsociety in n8n Cloud

The FITsociety node is published for self-hosted n8n, but n8n Cloud approval has not yet been granted. Publishing on npm does not make the node available in Cloud automatically. This guide therefore assumes a self-hosted environment.

Community nodes or the FITsociety node is missing

Ask the n8n Owner or Admin to check whether community nodes are allowed in your environment and whether n8n-nodes-fitsociety is installed. Use n8n 2.44.6 or later. With multiple workers, every worker must have the same package version. Do not remove the package as the first recovery step: existing workflows may depend on it.

The connection test fails

• Use the full HTTPS URL with /public/v1 as API Base URL.

• Check that Company ID, Client ID and Client Secret belong together to the same company and n8n integration.

• Do not substitute credentials for Zapier, Make or another API.

• Check whether access is still active. For revoked or replaced access, request new details through the company administrator and FITsociety support.

A successful connection test confirms the connection to the company profile. It does not prove the credential may perform every action. If only a particular feature is missing, have the assigned permissions checked.

An action returns an access, search or validation error

• 401 or invalid connection: check the credential and whether company access remains active.

• 403 or insufficient permissions: have the required action or data permissions reviewed. A read credential cannot change a member.

• 404 or not found: check the company and correct Client ID or Booking ID.

• 409 or conflict: check whether the record already exists or a retry key is being used for changed input.

• Invalid input: check required fields, dates, time zones and allowed custom field values.

• 429 or too many requests: reduce concurrency and respect the indicated waiting time before retrying.

For a member search with no results, use the exact email address and check status filters. Calendar and booking searches allow a maximum range of 92 days.

The trigger receives nothing

1. Check whether the workflow is active or published and the correct Events are selected.

2. Check whether the credential has webhook permissions and required data confirmations. A successful ordinary search does not prove this.

3. Have the n8n administrator check the public HTTPS webhook URL and reverse proxy settings. FITsociety must be able to reach the URL directly; localhost, private addresses and redirects are rejected.

4. After changing URL, Events or credential, disable and re-enable the workflow.

5. Create a new matching test event and inspect execution history. Old events are not resent automatically.

A signature or timestamp message

The trigger checks that a message genuinely comes from FITsociety. Have the administrator check the server clock and proxy, and confirm the original webhook content is forwarded unchanged. Do not disable this check. After replacing Client Secret, trigger workflows must be reactivated.

An action runs twice

Webhook delivery can be repeated. Use the original event ID for deduplication and the Business Event Key of FITsociety write actions. Do not use a random new ID on every retry. Also check the receiving app's duplicate-processing protection.

Support assistance

Provide company name, n8n version, FITsociety package version, resource and action or trigger, error message and time with time zone. Include execution ID if available. Obscure keys, tokens, webhook secrets and member data in screenshots and workflow exports. Do not include Client Secret in support messages.

Also read

• Connecting n8n to FITsociety on your own n8n environment

• Building workflows with n8n: FITsociety actions and triggers