Zapier overview and setup

The Uptivo app for Zapier is the simplest way to connect Club API data to other services without building and hosting an API client. It provides instant triggers, targeted searches, and guided actions backed by the same Club API documented in this portal.

Use the Club API directly when you need a custom user experience, an unbounded historical synchronization process, or an operation that the Zapier app does not expose.

App availability

Uptivo is available as a public integration in the Zapier app marketplace. Select Uptivo when creating a Zap. Club API access and the credentials described below are required.

Prerequisites

Before you connect an account:

1. Confirm that Club API access is enabled in the club’s Uptivo license. See Club API access.
2. Obtain the Subscription Key for the integration.
3. Create a Club API Key for the club from the Club API page in Uptivo. See Manage Club API access.
4. Choose the Club API Key permission that matches the Zap:
   • Read supports searches and read actions.
   • ReadWrite is required for write actions and instant triggers. Instant triggers use this permission to manage their webhook subscriptions.

The Subscription Key identifies the integration. The Club API Key selects the club and grants access to its data. For more detail, see Authentication.

Connect an Uptivo account

1. In Zapier, add an Uptivo trigger, search, or action to a Zap.
2. Select Connect a new account.
3. Enter the Subscription Key in API Gateway Subscription Key.
4. Enter the Club API Key in Club API Key.
5. Complete the connection test. Uptivo reads the club profile and labels the connection with the club name and ID.

Create a separate Zapier connection for each club. The same Subscription Key may be used with different Club API Keys when the integration is authorized for multiple clubs.

Create your first Zap

A simple first workflow is New Athlete followed by an action in another service:

1. Select New Athlete as the Uptivo trigger.
2. Connect the club with a ReadWrite Club API Key.
3. Test the trigger and inspect the sample Athlete fields.
4. Add a destination action that creates or updates a record.
5. Map the Uptivo Athlete ID as the stable external identifier. Treat email and other profile fields as attributes that may change.
6. Test the complete Zap, then turn it on.

Zapier supplies sample data while the Zap is being configured. After the Zap is turned on, each supported Uptivo event starts a Zap run.

Continue with the complete trigger catalog, the actions and searches catalog, or the possible uses and workflow examples.