Integrations connect the other platforms your staff uses, like force plates, GPS pods, velocity trackers, and athlete management systems, so their results arrive in FYTT as measurements instead of being typed in. This article covers connecting a provider, matching athletes, choosing metrics, when data syncs, what to check when data is missing, and what each provider needs.

Click Organization Settings (1) at the bottom of the left sidebar, then the Integrations tab (2). Integrations belong to the whole organization, not one team, and only managers see Organization Settings. Integrations aren't included on every plan. If the tab shows an upgrade prompt, check your plan in Billing.

Each row shows the integration's name and its status: Active, Failing, or Inactive. Click a row to open its panel. The panel shows the status, who connected it under Created by, and the provider's own rows: its athletes, its metrics, and any provider settings.

FYTT checks the credentials with the provider before saving anything. If they're refused, the panel says [Provider] rejected those details and nothing is saved. Check that everything was copied in full and try again.

Most providers start their first sync as soon as you connect, and the panel shows Sync in progress until it finishes. You can close the panel while it runs.

Data only imports for athletes FYTT has matched to someone in the provider. The Athletes row in the panel shows how many are matched, for example "12 of 30 athletes matched".

FYTT matches automatically on every sync. It tries email first, then first and last name together. Case and extra spaces are ignored, but spelling isn't, so "Katie" and "Katherine" won't match. Catapult and 1080 Motion send no emails, so they match on name only.

To fix a match, click Athletes. Each row is a FYTT athlete. In the [Provider] Athlete column, pick the person they are in the provider, or clear the cell to unmatch them. Changes save as you make them, and later syncs never overwrite a match you set by hand.

Most providers sync only the metrics you choose. Click Metrics in the panel (Parameters for Catapult, Forms for Teamworks), switch Sync on for each one you want, and click Save.

The first sync after that creates each chosen metric in your organization, named after the provider's metric and usually its test, like "Jump Height (Countermovement Jump)". After that it behaves like any other metric in reports, leaderboards, and automations. See Metrics for editing a metric's name, unit, or direction.

FYTT checks every connected provider for new data on a daily schedule. An integration only syncs once it has something to sync: metrics chosen, and for VALD, an organization picked. When a sync finishes, any automations that respond to new data run for each team.

To sync now, click the Manual sync button (the circular arrows) at the top of the panel. Enter how many hours to look back (24 by default) and click Sync. The panel shows Sync in progress until it's done.

Check these in order:

If the provider stops accepting your credentials, for example because a token was deleted or expired, the status changes to Failing and syncing stops. The panel shows Integration failing with the credential fields. Enter them again and click Save to switch it back to Active. Catapult, Hawkin, and VALD also email a notice to whoever connected the integration. A failing Teamworks integration shows Integration error instead. Contact support if it doesn't clear.

To rename an integration, click Rename (the pencil) at the top of its panel, change the Name, and save.

To disconnect, click Delete at the bottom of the panel, then Delete integration to confirm. Nothing more syncs in either direction. Metrics, measurements, and injuries already imported stay in FYTT.

Force-plate test results from Hawkin Cloud: jump, isometric, and other tests.

Connecting: in Hawkin Cloud go to Settings → Integrations, create a key, and copy the Token. Hawkin shows it only once. Paste it into Token in FYTT. API URL is filled in for Hawkin's default region; if your organization is hosted in another region, replace it with the API URL shown next to your token.

Metrics: the list shows every Hawkin metric by Test and Name. When an athlete tests more than once in a day, FYTT keeps one value. Set Same-day values default above the table to Best, Most recent, or Average, or override it for one metric in its Same-day values column. Height, distance, speed, weight, and time metrics come in as FYTT measurement types, so you can change their units. Anything else, like force or power, keeps Hawkin's own unit label.

ForceDecks, NordBord, and ForceFrame test results.

Connecting: email [email protected] to request API access. VALD issues a Client ID and Client Secret that cover all three products. After connecting, the panel has four rows:

When an athlete has several trials or tests in a day, FYTT keeps the best result.

GPS and inertial workload from Catapult wearables.

Connecting: sign in to Catapult as an administrator and create an API token set to never expire. Paste it into Auth token and choose the Base URL your account is hosted in: North and South America, Asia Pacific, Europe, Middle East and Africa, or China.

After connecting: Catapult doesn't sync when you connect, so the Athletes and Parameters lists start empty. Run a manual sync once to load them, then choose Parameters (Catapult's name for metrics). Catapult sends no emails, so athletes match on first and last name only.

GPS session data from PlayerData pods: Total Distance, High Intensity Distance, Sprint Distance, Max Speed, Average Speed, Metres Per Minute, Accelerations, Decelerations, High Intensity Events, and Sprints.

Connecting: ask PlayerData to enable a service account for your organization. They'll issue a Client ID and Client Secret. The service account must be listed as staff on every club you want data from, because a club it isn't on imports nothing. The Clubs row in the panel lists the clubs it can see. When an athlete has more than one session in a day, FYTT adds up totals, keeps the highest peaks, and averages rates.

Velocity, force, power, and sprint data from 1080 Sprint and Quantum sessions.

Connecting: sign in to the 1080 web app as an administrator, open the account menu, choose API Keys, and create a key. Paste it into API Key.

Metrics: the list covers the exercise types your account recorded in the last year. The Exercise types row in the panel shows how many there are. If the list is empty, record a session in 1080 and sync. Eccentric values are separate metrics, marked "(Ecc)". Athletes match on first and last name only, using the name shown in 1080.

1080 sprint results come in as ordinary metrics. To model an athlete's sprint mechanics from split times, see Sprint profiles.

Teamworks AMS data, in both directions.

Connecting: a FYTT connector has to be set up in your Teamworks account first, so contact FYTT support to request one. Then enter your Teamworks Username, Password, Server, and Site. The first import of athletes and forms takes a minute or two.

Forms (Teamworks to FYTT): click Forms, switch Sync on for the forms you want, and click Save. Open a form, click Activate, and switch on the fields to import. Only number fields are listed. Click a field and choose the FYTT metric it fills under Sync into metric.

Metrics (FYTT to Teamworks): click Metrics and switch on the FYTT metrics to send. They arrive in Teamworks as events on a form named "FYTT Data".

Injuries recorded by your athletic training staff in Healthy Roster.

Connecting: ask your athletic trainers or Healthy Roster support for API credentials for your healthcare provider account. Enter the Application ID, Application Secret, and Healthcare Provider ID.

FYTT imports your Healthy Roster organizations and athletes, matches athletes by email and then name, and imports injuries for matched athletes every night. The panel shows Organizations, Last synced, and how many Injuries have been imported. Imported injuries appear on the athlete's profile and in injury reports. See Injuries.

Velocity-based training sets from Vitruve encoders.

Connecting: in Vitruve, an organization owner goes to Settings > Integrations, opens the Exports tab, and clicks Create new for FYTT. Paste the key into API token.

Vitruve has no Athletes or Metrics rows. FYTT matches athletes by email, and the email must be the same in both platforms. Every metric Vitruve records syncs, named "Vitruve", then the exercise, then the metric, and holds the average of the set's reps. Vitruve doesn't check the key when you connect, so if nothing arrives after a day, delete the integration and connect again with a new key.

To push data from your own systems, choose API in New Integration, give it a Name, and click Create. The panel shows an Auth token with a Copy button for your developer to use with FYTT's API. Keep it private: anyone with the token can read your organization's data and add athletes and measurements through the API.

Export a spreadsheet from the device and upload it. See Importing data.