Once created, connectors are all gathered in the Connected users section of the App details page, where you can add, rename, view details, and delete them.
Find existing connectors
On the Apps page, click an App card to open its details page. The page has two sections:
| Section | Contents |
|---|
| Connected users (N) | Every connector under that App, where N is the count |
| Available tools | The tools that App generates, with the input and output parameters of each |
Each connector card shows the name, status, and creation time, for example Connected, Created at: 2026-08-25 14:40:32.
Connect multiple accounts under one App
You can create multiple connectors under one App, and they do not interfere with each other. Common uses:
| Scenario | Example |
|---|
| Environment isolation | One MySQL connector points to the test database, another to the production database |
| Content partitioning | One file connector holds product documentation, another holds internal policies |
| Account separation | One Yuque connector uses the team account, another uses a personal account |
| Permission tiers | One connector is read-only, the other is writable |
Click the Connect new user card in the Connected users section to create another one. The flow is identical to connecting for the first time.
For Apps that require an auth config, multiple connectors can share the same config or each use its own. The typical reason to use different configs is that the two accounts have different credentials.
Rename
The connector name is the main way to tell similar connectors apart, and you can change it at any time after creation.
Click the edit icon to the right of the connector name, the name becomes editable, and you confirm once you are done. The input box has a character counter in the lower right, with a limit of 64 characters.
Be specific with names. Product documentation library is far more useful than connector 1, especially when one App has several connectors.
View details
Hover over a connector card, and two buttons appear below it: Details and Delete. Click Details to see the full information about that connector.
These two buttons appear only on hover. They are not visible when the card is idle.
Delete
- Hover over the card: Move the pointer over the connector card you want to delete and wait for the buttons to appear.
- Click Delete: Click Delete. The console opens a confirmation dialog titled Delete the connected account, with the message: this action permanently disconnects the account. You can reconnect later, but any existing configuration may be lost.
- Confirm: Once you have verified everything, click Delete in the dialog. After the deletion succeeds, the connector disappears from the list. To cancel the operation, click Cancel.
Deletion cannot be undone. After a connector is deleted, the agents and clients that depend on it immediately lose the corresponding tools, and running tasks may fail. In production, confirm that no task is currently using the connector before you proceed.
Deleting a connector does not delete the auth config it uses. The config remains in the Auth configs list and can be reused by new connectors.
Status and expiration
| Status | Meaning | What to do |
|---|
| Connected | The credentials are valid and the tools are available | Nothing to do |
| Expired | The credentials are no longer valid and tool calls fail | Update the credentials in the auth config, then rebuild the connector |
Credentials most often become invalid because a token expired in the target system, a key was rotated, or an OAuth app was disabled. For troubleshooting, see OAuth 2.0 configuration and API Key configuration.
Unsupported operations
| Operation | Description |
|---|
| Change the connector type | It cannot be changed after creation; you can only create a new one |
| Restore a deleted connector | Deletion cannot be undone; you need to create it again |