Add services when you need them
Open Integrations for links to your workspace data and each project's Connected services, plus the provider library. Add a service because it solves a real job: scheduling, video, email or another capability your project needs.
You do not need to configure every card before you start building.
Understand the connection status#
A provider in the catalogue is an option to review. A saved repository or domain link is a reference. Neither means account access has been granted or an integration is working.
For a hosted project, Connected services shows its hosting and builder state; open it from the project's Project options or from Connections by project. Verified by a successful request means the builder has successfully called the project API; it does not mean it is continuously online or that all data sources are connected.
Managed foundation and outside providers#
MovePacket operates the supported hosting foundation under your account. You do not need your own Cloudflare account for that default setup.
Outside services retain their own account requirements, terms, subscriptions and limits unless a specific managed offer says otherwise. Adding a provider's name does not purchase a subscription or include its fees in Core.
Data & capabilities covers Data Connect and Event Intelligence. They are MovePacket capabilities, separate from adding an outside scheduling or video provider.
Athlete platforms feed Data Connect#
Intervals.icu is the first planned coach connection. Find it under Athlete platforms in the provider library. It is marked Planned · Not connected; requesting it does not start a sync or grant account access.
Your builder will use MovePacket Data Connect for the supported data. Provider authorisation sets the access boundary; future coach filters can narrow it. Intervals.icu for coaches explains the current access limitations.
Keep service credentials out of chat#
MovePacket does not yet provide a generally available customer credential vault or automatic connection broker. Nango is not an active customer connection feature. Do not send provider keys to an agent or paste them into a project description in anticipation of that feature.
Use only a supported, explicitly authorised connection flow. If one is missing, ask MovePacket about the provider and intended operation before supplying credentials. A recommendation is not a security approval for arbitrary API access.
Request another provider#
Use the provider request option in Integrations. Describe the job, provider and operations you need. Leave passwords, keys and private customer records out of the request.
A request can be reviewed for manual help or future support. A response such as under review or planned does not activate a connection. The connection needs its own permissions, verification and billing arrangements.
GitHub remains optional#
A repository can help you keep source history and collaborate, but the current MovePacket field only saves its link. It does not create a repository, connect GitHub or enable pull-request deployments. Your builder can use your existing GitHub setup, or work from a local folder with MovePacket's saved-update workflow.
Supplier documents without the hunt#
Expand Supplier documents on a provider card for its official legal and security sources. In Settings → Security & recovery, choose Build your evidence pack under Supplier evidence to select suppliers and download a dated document index. The index includes public links and a collection checklist, not saved supplier documents or signed agreements. See Supplier evidence.