Use the node FITsociety to retrieve or change data. Use FITsociety Trigger when a FITsociety event should be the starting point. Which actions can actually run depends on your company credential's permissions.

Available actions

• Client: search, retrieve, create, update contact details and invite.

• Tag: retrieve tags and add or remove them from a member.

• Coach: retrieve coaches and assign a coach to a member.

• Booking: search, retrieve, create, cancel and update attendance.

• Calendar Event: retrieve calendar events.

• Form: retrieve forms, assign an intake and schedule a check-up.

• Custom Field: retrieve field definitions and member values, and change editable values.

Receiving an event grants no extra write permissions. For example, invoice events are available as triggers, but the node has no general create-invoice action. Normal business rules, available products and balances still apply to bookings.

Example: searching for and retrieving a member

1. Create a workflow with a Manual Trigger.

2. Add FITsociety with Client → Search and filter by a test member's exact email address.

3. Add a second FITsociety node with Client → Get.

4. Map Client ID from search output to Client ID in the second node.

5. Run the workflow and check output. Add a condition if a search may also return no results.

Starting a workflow from FITsociety

FITsociety Trigger offers 56 events covering members, bookings, invoicing, forms, measurements, goals, habits, documents and conversations, among others. An event is not a full export of the underlying record. Check received fields before using them further.

1. Add FITsociety Trigger as the starting node.

2. Select the correct company credential.

3. Under Events choose one or more suitable events.

4. Add the desired next step and any filters.

5. Save and activate or publish the workflow, depending on the term used in your n8n version.

6. Then perform a matching test action in FITsociety and check execution in n8n.

Activation registers the subscription automatically. You do not need to create a generic webhook manually in FITsociety. Your credential does need webhook permissions and required separate consents for health data and private communications. Read access to members alone is insufficient.

For triggers, n8n must be reachable through a public HTTPS webhook URL. A localhost or internal-network-only address does not work. After changing Events, webhook URL or credential, disable and re-enable the trigger workflow to update the subscription. Historical events are not automatically replayed.

Processing repeated events safely

An event may be delivered again, for example after a temporary connection failure. Use the id of the event to recognize duplicate processing downstream. For FITsociety write actions, map this ID to Business Event Key, so repeated execution recognizes the same intended action within the retention period. Use different keys or nodes for separately intended changes. This is not an unlimited guarantee against duplicate processing across all connected apps.

Entering data carefully

For calendar and booking searches, choose a range of at most 92 days. Use YYYY-MM-DD for dates and include a time zone for times. For custom fields, change only selected fields; zero and false remain valid values. Intentionally clear a value with null. Company validation still applies.

Test write actions only with designated data. Client Create may link an existing account and send an email about it. Client Send Invitation sends a real invitation. The FITsociety node can also serve as a tool for a configured AI agent; limit available actions and data to that agent's needs.

Also read

• Connecting n8n to FITsociety on your own n8n environment

• n8n not working: checking installation, connection and triggers