App catalog
All Apps supported by Connector, how each one is connected, and what you need to prepare.
The Apps page in the left navigation of the console lists every system you can connect to. Each card represents one type of App, and the number on the card indicates how many connectors you have already created under that App.
The top of the page provides three filter tabs and a search box:
| Tab | Meaning |
|---|---|
| All | Shows all Apps, whether or not they are connected |
| Connected | Shows only Apps that have at least one usable connector |
| Expired | Shows only Apps whose credentials are no longer valid and need to be reauthorized |
First decide whether an auth config is needed
This is the single most important thing to determine before you connect. Apps fall into two categories:
For Apps that need a config first, see Authentication overview for the fields and where to obtain them.
Apps that require an auth config
| App | Authentication method | What you need to prepare |
|---|---|---|
| Salesforce on Alibaba Cloud | OAuth 2.0 | The org domain, plus the Client ID and Client Secret of an External Client App |
| MaxCompute | OAuth 2.0 | No credentials, only an optional authorization scope |
| Yuque | API Key | A Yuque token |
Apps that connect directly
Platform-hosted
Data is uploaded to Alibaba Cloud Model Studio, where the platform parses and hosts it. No credentials from an external system are required.
| App | Purpose | Generated tools |
|---|---|---|
| File connector | Hosts unstructured documents such as PDF, Word, and Markdown | Search files, Get file |
| Table connector | Hosts structured tabular data such as XLSX and XLS | Get table schema |
The connection dialog contains the connector name, the connector description, and Storage location. Storage location currently offers only one option, Use platform storage, which keeps the data within the limited free storage resources provided by the platform.
Alibaba Cloud Object Storage Service
| App | Purpose | What you need to prepare |
|---|---|---|
| OSS | Access files in Object Storage Service | An OSS bucket, with authorization completed and tags added |
The connection dialog contains the connector name, the connector description, and Storage bucket, with an Authorize now entry next to it.
Databases
Data stays in the original database and is accessed in real time. Configuration is completed by importing a data source from DMS.
| App | Purpose | What you need to prepare |
|---|---|---|
| MySQL | Connect to a MySQL database and run SQL queries | A MySQL instance registered in DMS |
| PostgreSQL | Connect to a PostgreSQL database and run SQL queries | A PostgreSQL instance registered in DMS |
| PolarDB-X 2.0 | Connect to a PolarDB-X 2.0 distributed database | A PolarDB-X 2.0 instance registered in DMS |
Select data source in the connection dialog offers Import a data source from DMS. As the console explains, this quickly imports a data source that already exists in DMS, so that data sources of all kinds are managed centrally through DMS.
DingTalk family
The connection dialog has a single field for the endpoint issued by the DingTalk MCP gateway. There is no connector name.
| App | Purpose | What you need to prepare |
|---|---|---|
| DingTalk Docs, DingTalk Sheets, DingTalk AI Tables, DingTalk To-Do, DingTalk Calendar, DingTalk bot messages | DingTalk office collaboration | One MCP endpoint with credential per App |
The button for these six Apps is Submit, not the Confirm used elsewhere.
Mailbox
The connection dialog has only two fields: Email address and Authorization code (generated after enabling the IMAP/SMTP service in the mailbox settings). The authorization code is stored encrypted.
| App | Purpose | What you need to prepare |
|---|---|---|
| QQ Mail | Access QQ Mail over IMAP/SMTP | A QQ Mail address and its authorization code |
| NetEase Mail | Access 163 Mail over IMAP/SMTP | A 163 Mail address and its authorization code |
The button for these two Apps is Submit, not the Confirm used by Apps that require an auth config.
Apps that connect through an authorization window
These Apps open no dialog. They open a separate window where you grant authorization in the target system.
| App | Purpose | What you need to prepare |
|---|---|---|
| Yunxiao | Access Codeup repositories, branches, commits, and change requests | Signed in to Yunxiao in the browser, with the account in the target organization |
| Tencent Docs | Read, create, and edit Tencent Docs | The browser can reach Tencent Docs; sign in to a Tencent Docs account when authorizing |
NoteConnector is in beta, and the App list and the connection capability of each App are being released progressively. The Apps page in the console may show Apps this documentation does not cover yet, so refer to what the page actually displays.
Common fields
Apart from the Apps that require an auth config, the DingTalk family, the mailbox Apps, and the Apps that connect through an authorization window, every connection dialog contains the following common fields:
| Field | Required | Description |
|---|---|---|
| Connector name | Yes | Distinguishes multiple connectors under the same App. Up to 64 characters |
| Connector description | No | Describes the data content and its purpose. It affects how accurately an agent selects tools |
The remaining fields depend on the App type. See the detailed instructions for each App.
Manage existing connectors
In the Connected users section of an App details page you can add a connector, rename one, view its details, and delete it. For the full description, see Connected accounts.
WarningThe connector type cannot be changed after creation. To change it, you have to create a new connector.
ImportantIf you are not sure which App to start with, use the File connector to walk through the workflow first. It requires no external credentials and no auth config.