I cannot find FITsociety in Zapier
Open the invitation through FITsociety → Settings → Plugins and integrations → Zapier → Connect to Zapier. The integration is not yet available as a public app in the general catalog. Check that you are logged in to the correct Zapier account and have accepted the invitation.
My company is missing or I cannot authorize access
You need active manager or administrator access and permission to manage integrations. Check the logged-in FITsociety account. One connection accesses one company; a different company name in your Zap means you are using the wrong connection there.
The connection request expired
Start a new connection from Zapier and authorize again. Do not reuse an old authorization screen. If a message says permission is missing, reread the requested permissions and separate data confirmations.
The Zap does not start
Check whether the Zap is actually on and whether Zap history contains errors.
After enabling, create a new matching test event. Old records are not reprocessed automatically.
Using New Client or New Booking? Allow for your Zapier plan's polling interval.
Using an instant trigger? Check you selected the correct event and the intended action falls within the described trigger coverage.
Check filters and conditions: a Zap may start but stop before the action.
An empty trigger test does not automatically mean the connection is broken. There may be no recent matching events for this company. Editor sample data does not prove a real event has been received.
A member or booking cannot be found
Check the company connection and use the correct ID type. Find Client searches by exact email address. An event ID or company relationship ID does not work as Client ID. The booking dropdown covers the past 30 and next 60 days; enter Booking ID directly for bookings outside that window.
An action returns an error
Connection expired or unauthorized: reconnect the account. New features may require additional permissions and renewed authorization.
No access: check company permissions and allowed data. Retrying without restoring permissions will not resolve this.
Conflict or member already exists: search for the member first. Do not reuse a Source Event ID for changed input to the same action.
Booking rejected: check availability, product or balance, status and booking or cancellation rules.
Too many requests: let Zapier handle the indicated wait and retry; do not repeatedly run the same action manually.
A custom field is empty or has the wrong value
Select an editable field from the linked company. Automatic fields cannot be changed. Use YYYY-MM-DD for dates. Numbers may use a decimal comma without a thousands separator. An empty field does not automatically clear its existing value: deliberately use Clear Value for that. Zero and an unchecked checkbox are valid values.
Support assistance
Send company name, selected trigger or action, error message, time with time zone and failed Zap run ID. If needed, add a screenshot with keys, tokens and member details obscured. Never share passwords, Client Secrets or access tokens in a chat or public video.