Inspect detected services and integrations

Use Orbit’s detected integrations to understand a project’s external dependencies.

Before you start

Open the project or app folder whose dependencies you want to inspect. A service can exist in the product without being recognizable to the detector.

The empty state means Orbit did not recognize an integration in this project’s dependencies or configuration.

Step by step

1. Open Orbit → Integrations and read the detected service entries.

2. Use the available entry details as clues to the relevant package or configuration in Code.

3. Confirm how the application actually uses the service before changing its configuration or asking an agent to modify it.

4. If the view says No integrations detected, inspect the project scope and its dependency or platform configuration. The empty state describes detection, not a guarantee that the app has no external services.

5. After dependency or configuration changes, refresh or reopen the relevant project view and inspect the updated result.

6. For connection failures, check the application’s actual error and service configuration. Use detection to locate the integration, not to diagnose credentials by itself.

What to expect

You have a useful starting map of recognizable services and know which findings still need confirmation in the project.

Troubleshooting and useful details

The demo screenshot intentionally shows the real empty state. Detection does not create an account, authenticate a connection, verify billing, or test a service endpoint. Nested apps may need their own project scope to make the relevant configuration clear.