Skip to main content
All CollectionsIntegrations
Introduction to Integrations
Introduction to Integrations

Learn the basics of setting up integrations in Arc

James Mckechnie avatar
Written by James Mckechnie
Updated over a week ago

There are a few different types of Integration that you may need to work with in Arc:
โ€‹

Athlete Integrations

These integrations will require you to send an invite link to athletes, to link their own accounts. This is most common with consumer-facing integrations, such as Garmin, Oura and Whoop.

Coach Integrations

These integrations will require a coach to link their third-party account to Arc. After linking the integration, the coaches athletes will be pulled into the system so that you can match them up to Arc athletes. Arc will attempt to automatically match names for you, but will often have trouble matching people with nicknames.

External Integrations

These integrations must be set up inside the third-party app rather than Arc. The most common of these is Teambuildr, where you must provide your Arc URL to Teambuildr to link with us.

Manual Integrations

These integrations can provide us data via the cloud, but don't provide an easy way for your to link it yourself. Most times, this means contacting their customer support (or ours), to obtain special credentials. Once we have these credentials, we can link up with the integration on our end for you.

Importers

These integrations don't actually provide an interface for us to integrate via the cloud. Instead, you will need to export data from the system and upload it into Arc. Similar to Coach integrations, Arc will do its best to match data from your export to Arc athletes, but you may need to configure your integration to match up some names. This is most common with GPS devices.

To see more info on how to link integrations see here.

To see more information about specific integrations see here.

Did this answer your question?