# Connectors

Connect your apps, check their available operations, and read or change the right information.

A connector gives Vision access to an app, account, local folder, or device service. Use it to read current information or perform the operations that app exposes. Some connectors also collect records for later search.

You can use a ready connector before a historical import finishes. Connecting an account, running an operation, and collecting its history are separate steps.

## Connect your first app

Open **Local connection help** from the computer where Vision is installed:

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

Use your existing Vault directory. If your installation has a saved binding, `zortex help` opens the same view without entering the path. Leave the terminal running while the help page is open.

Find your app under **Connections in progress**, **Ready to use**, or **Unavailable**. Open an incomplete app's setup or authorization control, complete the provider's steps, and return to the help page. A ready row tells you whether Actions are available or a read has succeeded. [Connect an app](/docs/vision/connectors/connect) explains each state and control.

If you already have an agent, ask:

### Agent host

> Connect my work calendar, check which account is selected, and show my next three meetings.

The agent should complete the available setup steps, inspect the calendar operation, and return the meetings. It should ask only for a necessary account choice or input it cannot obtain.

## Choose the next guide

### [Connect an app](/docs/vision/connectors/connect)

Set up an app or finish sign-in.

### [Accounts and permissions](/docs/vision/connectors/accounts)

Check an account, workspace, folder, or permission.

### [Coverage and freshness](/docs/vision/connectors/coverage)

Understand what a source can read.

### [Sync your sources](/docs/vision/connectors/sync)

Collect information for later search.

### [Find supported apps](/docs/vision/connectors/sources)

Find a source and its available tools.

### [Recover a connection](/docs/vision/connectors/recovery)

Repair a failed connection.

## Use a ready connector

From an agent, discover the source's operations with `indra.actions`, inspect the chosen method, and call it through `indra.action`. From a terminal, the equivalent discovery command is:

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

Replace `gmail` with the exact source ID from your installation. The result tells you what that source offers; it does not execute those operations. Follow [Discover tools](/docs/vision/tools/discovery) and [Run an action](/docs/vision/tools/actions) for a complete example.

## Understand readiness

| Result | What you can conclude |
| --- | --- |
| App appears in the directory | Vision knows about that route; setup may still be needed. |
| Actions are available | You can inspect the available operations. No business operation is implied. |
| A read succeeds with no items | The read worked and returned an empty result for its scope. |
| Local records exist | Some information has been retained; the account may no longer be connected. |
| An operation returns the requested result | That operation worked for the selected account and resource. |

An unavailable app should name its missing prerequisite. Other ready apps remain usable while you resolve it.
