# Find supported apps

Find a source on your installation and discover what it can actually do.

The useful app list is the one in your installation. A directory entry can describe a possible integration even when its provider, configuration, account, or operating-system access is missing.

## Find an app in connection help

Run `zortex help`, or use an explicit Vault:

```sh
indra --root "/absolute/path/to/your/Vault" help
```

Find the app's displayed name. Ready apps are grouped under **Ready to use**; sources that cannot currently run appear under **Unavailable** with a reason. Setup forms may request a local folder, provider client, tenant, region, library, or local service port.

Do not infer readiness from the number of directory entries. Check the row for the app you need.

## Find its machine identifier

For terminal or agent work, list the current sources:

```sh
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"sources"}'
```

Use the returned `source` value in subsequent calls. Common identifiers include `gmail`, `google-drive`, `google-calendar`, `google-chrome`, `microsoft-edge`, `computer-files`, `browser-use`, and `cua`. Their presence here is an example of naming, not a promise that each is ready on your computer.

Source IDs and plugin IDs serve different purposes. A source ID selects an app's operations; a returned `indra-source-...` plugin ID controls whether its provider is enabled.

## Inspect the app's operations

For a returned source:

```sh
indra --root "/absolute/path/to/your/Vault" actions --json '{"source":"google-drive"}'
```

Choose the actual method that fits your task, then inspect its arguments:

```sh
indra --root "/absolute/path/to/your/Vault" actions --json '{"source":"google-drive","method":"<method-name-from-the-catalog>"}'
```

The catalog identifies current operations and their input schemas. Where supported, use its returned pagination and filters to narrow a large list. Follow [Discover tools](/docs/vision/tools/discovery) before invoking a method.

For a source with only a shared bounded read, inspect `method:"connector.read"`. This is executed as the shared `connector.read` Action, not as an arbitrary provider method.

## Recognize different setup needs

| Source type | Typical prerequisite | Where to continue |
| --- | --- | --- |
| Hosted app | Provider sign-in, consent, and sometimes an approved client | The live authorization page opened by connection help |
| Local folder or document library | An explicit existing folder or library selection | The source's setup form |
| Browser data | The selected local browser profile and its access | Source setup and operating-system permission |
| Native application or helper | Installed application, compatible local service, and OS access | The source's stated prerequisite |
| Browser or computer Actions | A working browser transport or native driver | [Browser and computer](/docs/vision/browser-computer) |

These are setup categories. The source's actual form and catalog determine the supported details.

## If the source is absent

Inspect source plugins:

```sh
indra --root "/absolute/path/to/your/Vault" manage --json '{"what":"plugins","about":"drive","limit":25,"offset":0}'
```

Follow `nextOffset` if the inventory is paginated. A disabled installed source can be enabled through its observed plugin ID. If no provider is installed, the public directory alone cannot supply it. Check the supported installation or configuration path before retrying.

Do not replace a missing connector with another account or claim that a similar app has equivalent coverage. Use an authorized browser or computer route only when it can complete the same task and preserve the required account and result.
