A Zap starts with a trigger: the event that starts automation. One or more actions follow. FITsociety can start a Zap or perform an action after an event in another app.
Which triggers can you use?
The integration includes instant event triggers for members, bookings, invoices and payments, forms, progress and documents, among others. Choose the event matching your process exactly. A trigger passes on an event; it does not automatically retrieve a complete member record or all form answers.
There are also New Client and New Booking. These periodically check for new records. Polling interval depends on your Zapier plan. New Client also responds when an existing FITsociety account is linked to your company. New Booking may include waitlisted and pending bookings: add a status filter if you only want confirmed bookings.
Some instant triggers are still named Client Created via API or Booking Created via API. Also read the trigger description; the updated integration includes supported ordinary app actions too. Do not choose both periodic and instant triggers for the same downstream process without handling duplicates.
What can you have FITsociety do?
Find a member by email address or ID, create a member or update contact details.
Send an invitation, add or remove tags and assign a coach.
Assign an intake form or schedule a check-up.
Find, create or cancel a booking and update attendance.
Change an editable custom member field.
An invoice event, for example, does not mean a create-invoice action also exists. Zapier's action menu determines available operations. Bookings and cancellations still follow your company's normal booking, balance and cancellation rules.
Example: adding a tag after a form submission
Choose the app where the form is completed as the trigger.
Add FITsociety → Find Client and map the submission's email address. This search uses the exact email address, case-insensitively.
Only let the Zap continue if a member was found.
Add Add Tags to Client . Use the Client ID from the search step and select an existing tag.
Map the form submission's unique ID to Source Event ID.
Test with a test member, check the tag in FITsociety and enable the Zap.
Which ID do you use?
For member actions, always use Client ID. In New Client, the general field ID is the company relationship ID, which is different. In an instant event, the general ID is the event ID. Use an available Client ID from the event or retrieve the member first with Find Client by ID. A booking action requires Booking ID.
Preventing duplicate actions
Every write action requires a Source Event ID. Map the original event's unique, persistent ID here. Do not use fixed text for all new events. FITsociety recognizes the same action on repeated attempts for 24 hours. If the same action intentionally makes two changes to the same record, give the steps different fixed Action Step ID values. Also check other apps' own duplicate-processing protection.
Please note when testing
An action test can change real data or send email. Create Client creates a new account without an invitation email; an existing account is linked directly to the company and may receive an email about it. Send Client Invitation sends a real invitation. Search for existing members first and test only with designated data.
Use the integration for new events. Historical information is not synchronized automatically. Periodic triggers read at most the 500 newest records per check and are not intended for large imports.