Overview
Integration Center is a one-stop platform for integrating third-party capabilities provided by CloudBase. It packages common third-party services (WeChat Pay, WeChat Official Account, SMS, customer service, AI, and more) into ready-to-use "integrations". Developers no longer need to build their own backend, manage credentials, or handle signature verification and decryption — just fill in the required parameters once in the console, and the platform automatically generates the corresponding cloud functions and callback pipelines. The business side can then call them via the cloud function SDK or HTTP.
Why Integration Center
When integrating with third-party services, developers typically face the following repetitive work:
- Credential management: Secure storage and rotation of API keys, certificates, secrets, and tokens
- Signing and verification: Cryptographic logic for request signing, callback signature verification, AES-GCM decryption, etc.
- Callback routing: Provisioning domains, configuring HTTPS, forwarding to business functions
- Error handling: Network retries, timeouts, risk control, idempotency
- Environment variable injection: Injecting credentials into the function runtime in a controlled manner
Integration Center precipitates the templated logic above into the platform layer, so developers can focus solely on business logic itself.
Core Capabilities
| Capability | Description |
|---|---|
| Unified credential hosting | Sensitive information such as API keys, certificates, and private keys is managed by Integration Center and never appears in business code |
| Callback receipt and verification | Asynchronous notifications from third parties are automatically received, verified, and decrypted, then forwarded to the business function in plaintext |
| One-click function deployment | When you create an integration, the corresponding HTTP cloud function template is generated automatically; the business side only needs to fill in business logic |
| Environment variable injection | Credentials, callback URLs, and other configuration are auto-injected into the function runtime as environment variables |
| Visual management | Integration status, callback URLs, associated functions, and other information are viewed and edited uniformly in the console |
How It Works
┌─────────────────┐ ┌─────────────────┐ ┌────────────────────┐
│ Integration │ │ Integration │ │ Auto-generated │
│ Center Console │ Create │ Instance │ Inject │ Cloud Function │
│ │────────►│ │────────►│ │
│ Fill credentials │ │ Hosts credentials │ │ Env vars │
│ once │ │ Generates callback URL │ │ Business logic │
└─────────────────┘ └────────┬────────┘ └─────────┬──────────┘
│ │
│ Receives async callback │ Called by business side
│ Auto verify + decrypt │
▼ ▼
┌─────────────────┐ ┌────────────────────┐
│ Third-party │ │ Third-party API │
│ service │ └────────────────────┘
│ (WeChat Pay…) │
└─────────────────┘
End-to-end flow:
- Create integration: In the console, choose an integration type (e.g. "Mini Program WeChat Pay") and fill in the required credentials and configuration
- Platform deployment: Integration Center automatically generates an HTTP cloud function (named like
<integration-name>-<random-string>) and injects credentials as environment variables - Business invocation: The frontend or another backend calls the integration function via the cloud function SDK / HTTP to perform active requests (placing orders, querying orders, etc.)
- Callback handling: Asynchronous callbacks from third-party services first reach Integration Center for signature verification and decryption, then are forwarded to a specific route on the cloud function in plaintext
Supported Integration Types
| Category | Integration | Typical Scenarios |
|---|---|---|
| Payment | Mini Program WeChat Pay | Mini Program / Official Account / Native QR / H5 payments — covers ordering, querying, refunding, and callbacks |
| Official Account | WeChat Official Account | Web authorization, user messages, template messages, custom menus |
| AI | AI LLM Integration | Credential hosting and unified invocation entry for major LLM APIs |
| Notifications | SMS / Email | Verification codes and notification messages |
| Customer Service | Smart Customer Service | Customer service session integration, script management |
Integration types are continuously expanding. The latest list is subject to the Integration Center console.
Comparison with Traditional Integration Approaches
| Aspect | Self-built Integration | Integration Center |
|---|---|---|
| Credential storage | Self-selected (env vars / config center / KMS) | Hosted by the platform, auto-injected |
| Callback domain | Self-purchased domain + HTTPS cert + configuration | Auto-generated and maintained by the platform |
| Verification & decryption | Self-implemented cryptographic logic | Handled by the platform; business side receives plaintext |
| Retries and idempotency | Self-handled | Platform provides basic retries; business side still must ensure idempotency |
| Upgrade and maintenance | Self-tracked third-party API changes | Platform syncs template updates |
| Onboarding time | Days to weeks | Tens of minutes |
When to Use
Integration Center is suitable for the following scenarios:
- Quick onboarding for new projects: You want to wire up third-party services and ship an MVP in the shortest possible time
- Limited backend resources: Frontend-only / low-code / individual developers who want to avoid building a separate backend
- Focus on business rather than infrastructure: You want to spend energy on business logic rather than maintaining credentials and callback pipelines
- Multi-channel unified integration: Mini Program, H5, PC, App, and other channels share the same integration configuration
When not to use:
- Deep customization of the underlying pipeline is required: e.g. self-implementing callback signature algorithms or special routing of callbacks
- Extremely large-scale, high-concurrency: With strict QPS / SLA customization needs, integrating directly with third-party APIs is recommended
Next Steps
- Read the Usage Flow to learn how to create your first integration
- Refer to specific integration guides such as Mini Program WeChat Pay Integration Guide
- Visit the Integration Center console to get started