# uip is

> `uip is` is the Integration Service tool: it manages the connector platform that brokers OAuth connections to external SaaS and runs CRUD activities against them. The tool is organized around five resources — connectors (the catalog), connections (OAuth sessions for an account), activities (per-connector operation definitions), resources (connector objects and their data-plane operations), and triggers (event-driven connector operations). Install it with `uip tools install is`, or invoke `uip is …` and let auto-install run. See [Tools (plugins)](./concepts-tools.md) for the install model and [uip tools](./uip-tools.md) for the command that manages tool installation. `is` is the command prefix; the underlying package is `@uipath/integrationservice-tool`.

`uip is` is the Integration Service tool: it manages the connector platform that brokers OAuth connections to external SaaS and runs CRUD activities against them. The tool is organized around five resources — connectors (the catalog), connections (OAuth sessions for an account), activities (per-connector operation definitions), resources (connector objects and their data-plane operations), and triggers (event-driven connector operations). Install it with `uip tools install is`, or invoke `uip is …` and let auto-install run. See [Tools (plugins)](./concepts-tools.md) for the install model and [uip tools](./uip-tools.md) for the command that manages tool installation. `is` is the command prefix; the underlying package is `@uipath/integrationservice-tool`.

Most read commands cache responses per-tenant on disk to keep interactive use responsive; pass `--refresh` on any cached command to force a fresh fetch.

## Resources

Each resource has its own reference page. The verb set on each page matches the commands registered by `uip is` — run `uip is --help` to confirm the full surface on your installation.

| Resource | Purpose |
|---|---|
| [connectors](./uip-is-connectors.md) | The connector catalog — every integration the tenant can reach. |
| [connections](./uip-is-connections.md) | Tenant-side OAuth credentials/sessions for a connector. |
| [activities](./uip-is-activities.md) | The operations a connector exposes (`CreateTicket`, `ListAllRecords`, etc.). |
| [resources](./uip-is-resources.md) | Connector objects (tickets, contacts, files), with `describe` and runtime `execute`. |
| [triggers](./uip-is-triggers.md) | Event hooks (`CREATED`, `UPDATED`, `DELETED`) the connector can fire. |

## Synopsis

```
uip is <resource> <verb> [options]
```

Always `uip is`, never `uip integration-service`. `is` is the tool's command prefix (see the `commandPrefix` column in `uip tools list`).

## Common flags

A small set of flags recurs across the resource verbs. They behave the same way wherever they appear:

| Flag | Used by | Purpose |
|---|---|---|
| `-t, --tenant <tenant-name>` | every verb | Override the tenant selected at authentication time. Optional; omit to use the session default. |
| `--refresh` | cached read verbs (`list`, `describe`, `get`, `objects`) | Force a re-fetch from the API and update the on-disk cache. |
| `--connection-id <id>` | many verbs | Scope a request to one connection. Required by every `resources execute` verb; optional on metadata reads, where it lets the server include custom objects/fields. |

Verb-specific flags (filters, bodies, query parameters) are documented on each resource page.

## Global options and exit codes

All `uip is` verbs honor the four [global options](./global-options.md) (`--output`, `--output-filter`, `--log-level`, `--log-file`). Exit codes follow the shared [contract](./exit-codes.md).

## See also

- [Concepts: how UiPath CLI is organized](./concepts-cli-architecture.md) — where tools fit in the host + tool model.
- [Sessions](./concepts-sessions.md) — how tenant context is resolved.
- [Configuration](./configuration.md) — environment variables and config files that affect every tool.
- [`uip login`](./uip-login.md) — session used for all Integration Service calls.