The FITsociety n8n integration lets you build workflows between FITsociety and other services. It consists of FITsociety for actions and FITsociety Trigger for events that start a workflow.
Availability: this guide is for a self-hosted n8n environment. The package is published on npm; n8n Cloud approval has not yet been granted. You therefore cannot yet install it as an approved community node in n8n Cloud.
What do you need?
A self-hosted n8n environment, version 2.44.6 or later. This is the minimum supported and tested version.
An n8n Owner or Admin allowed to install community nodes.
Company-specific n8n access provided by FITsociety following company administrator approval.
For direct triggers: a publicly reachable HTTPS webhook URL for your n8n environment.
Request n8n access from FITsociety support and describe which data you want to read and actions you want to automate. Access is tailored to that need. An integration overview card does not create these details automatically. Zapier, Make or other integration credentials do not work here.
Step 1: Install the package
In n8n, open Settings → Community nodes.
Choose Install.
Enter the package name
n8n-nodes-fitsociety.Read and confirm the community node notice and click Install.
Check that the package is installed. This guide is based on version 0.1.2.
Use the FITsociety package on npm. Administrators can find additional installation information in the n8n documentation. In a multi-worker environment, the package must be available on every worker.
Step 2: Create the connection
Create a workflow and add the node FITsociety .
Under Credentials, create a new connection of type FITsociety OAuth2 API.
Under API Base URL enter the URL supplied by FITsociety. For production, this is
https://api.fitsociety.io/public/v1.Enter the matching Company ID, Client ID and Client Secret .
Save the credential and check that the connection test succeeds.
The connection test only reads the company profile and changes no data. No separate OAuth redirect URL is needed. n8n stores credentials encrypted. Store Client Secret only as a credential, not as workflow text or in screenshots or support messages.
Step 3: Perform a safe first test
Connect a Manual Trigger to the FITsociety node. Choose Resource: Client and Operation: Search. Under Filters, use a test member's exact email address and execute the step. Check that the expected member from the correct company is returned. Only then choose an action that changes data.
Multiple companies or ending access
Create a separate credential for each company using its supplied details. Disable a workflow to stop it. To revoke company access entirely, ask the company administrator or FITsociety support to revoke the relevant n8n credential pair. Stopping one workflow alone does not revoke its credential.