Zapier limits and troubleshooting

Connection and permission errors

An Uptivo connection requires both the Subscription Key and the Club API Key. If the connection test or a Zap step fails:

1. Confirm that Club API access is enabled in the club’s Uptivo license.
2. Confirm that the connection uses the Subscription Key supplied for the integration and a Club API Key created for the intended club.
3. Check that neither key was rotated or revoked. Reconnect the Uptivo account in Zapier after a key changes.
4. Use a ReadWrite Club API Key for write actions and instant triggers. A Read key supports searches and read actions only.
5. Confirm that the selected resource belongs to the connected club and that the license grants the required feature.

See Authentication and Manage Club API access.

An instant trigger does not run

Instant triggers require an active Zap and a ReadWrite Club API Key. Check that:

• the Zap is turned on;
• the Uptivo connection is still valid;
• the selected trigger matches the event that occurred;
• webhook delivery is healthy on the Club API page in Uptivo;
• the Zap was active when the event occurred.

Trigger activation manages its webhook subscription automatically. Do not create a separate Club API webhook subscription for the same Zap.

Webhook delivery may be retried, and consumers must not rely on events arriving exactly once or in a particular order. Use the event id to make destination writes idempotent. Use resource IDs to retrieve or match the current object when the latest state matters.

Booking and attendance are different

ClassParticipant events describe booking records. A newly created booking can be queued, and a booking can exist before the Class takes place. The NoShow value is a stored attendance signal, not independent proof that the Athlete was physically present.

Do not count New Class Booking as attendance. For attendance workflows, inspect the booking state and NoShow value after the relevant update, or use the Athlete attendance summary searches. See Class participants.

List searches and history

Bounded list searches return at most 200 records per Zap run. Their default Maximum Results value is 30. The app follows Club API pages and cursors internally until it reaches the requested maximum or the available results. You do not receive or manage the cursor.

If a later Zap step must process all returned records, select the option to return all matches and use the results as line items. Verify that the destination action accepts line items before relying on this behavior.

List searches are not a one-step full historical synchronization. They are designed for bounded lookups, reports, and small batches. For a complete import or a resumable synchronization over an unknown number of records, build a process directly against the Club API and its documented pagination model. See Pagination and synchronization.

Read-only resources

The Zapier app does not provide generic CRUD operations. The following areas are read-only even though you can search them or receive related events:

• Trainings and telemetry;
• Classes and the Class catalog;
• Subscription products;
• Challenges and Challenge results.

Contacts support the specific Set Contact Client Stage action, not generic Contact creation, editing, or deletion. Use only the write actions listed in Actions and searches.

Rate limits and large workflows

Zapier calls use the Club API limits of 50 calls per minute and 25,000 calls per 30 days. Large loops, repeated searches, or one search per line item can consume the quota quickly. Prefer event data and direct ID lookups over repeated list searches. See Rate limits.