Published at: 2026-10-12
Overview
Learn the applicable boundaries of prebuilt connectors, project connectors, and HTTP components.
Overview
A connector is a capability wrapper for connecting to a specific type of external system. For implementation consultants, prebuilt connectors can be configured directly, reducing development and adaptation costs.
Core Concepts
The platform provides two types of connectors for implementation consultants:
Type | Description |
|---|---|
Prebuilt Connector | A connector already listed on the platform and ready to configure |
Project Connector | A connector developed and accumulated through the connector development tool for a specific project or high-frequency system |
In addition, the HTTP component can be used to call APIs directly, but it is not equivalent to a connector. See “Difference Between HTTP Components and Connectors” below for details.
Connector Types
By source, connectors fall into two types: prebuilt connectors and project connectors. Prebuilt connectors are maintained by the platform, and implementation consultants can configure them directly. Project connectors are accumulated through the connector development tool for high-frequency or reusable systems.
Current Priority Connectors
For mature connectors already available on the platform, new projects should prioritize delivery through the System Integration Platform. Current priorities include:
- Kingdee Cloud
- Feishu Bitable
- Other connectors that are mature and have completed project validation
Difference Between HTTP Components and Connectors
HTTP components can call APIs directly, but they are not equivalent to connectors.
Dimension | HTTP Component | Connector |
|---|---|---|
Usage | Single or few API calls | System capability encapsulation |
Reusability | Lower or project-internal reuse | Cross-project reuse |
Configuration experience | Requires manual request parameter configuration | More standardized actions and objects |
Maintenance cost | More project-level maintenance | Uniform platform accumulation |
Applicable scenarios | Custom, lightweight APIs | High-frequency, standard, reusable systems |