Integration · Channels

Deploy Agents / Workflows where users actually live.

Supported Channels

Channel	Status
Web	✓ JS SDK / iframe
Mobile App	✓ iOS / Android SDK
DingTalk	✓ Enterprise IM
WeCom	✓ Enterprise IM
Feishu	✓ Enterprise IM
WeChat	✓ WeChat Official Account / customer service messages
Mini-program	✓ WeChat mini-program
API	✓ RESTful direct call
Desktop client	✓ Built-in

Web (JS SDK)

<script src="https://cdn.evose.ai/widget.js"></script>
<script>
  Evose.init({
    agentId: 'agent-12345',
    apiKey: 'pub_xxxxx',     // Public key for the front end
    container: '#chat-bubble',
    user: {
      id: 'user-internal-id',
      email: 'user@example.com',
    },
  });
</script>

Features:

Embeddable on any page
Auto-adopts theme color
SSO pass-through (already logged into your site → silent login)

iOS / Android SDK

// iOS
let evose = EvoseClient(apiKey: "pub_xxx", agentId: "agent-12345")
let chat = evose.openChat(in: viewController)

// Android
val evose = EvoseClient(apiKey = "pub_xxx", agentId = "agent-12345")
evose.openChat(activity)

DingTalk / WeCom / Feishu

General flow:

Create a bot / app on the enterprise IM platform
Get AppKey / AppSecret
Configure in Evose Integration · Channels
Fill in the callback URL on the IM platform: https://evose.example.com/api/channel/<platform>/callback
Verify message round-trip
Publish the bot to employees or groups

One bot, multiple Agents

A single DingTalk / WeCom / Feishu bot can route to multiple Agents (by user group / keyword).

WeChat Official Account

Channel: WeChat Official Account
AppID: wx-xxxxx
AppSecret: {{credential:wechat_secret}}
Default Agent on follow: agent-12345
Keyword routing:
  - "order lookup" → agent-orders
  - "refund" → agent-refund
  - other → agent-customer-service

WeChat Mini-Program

The mini-program needs to integrate the Evose JS SDK or call the API directly. Configuration is the same as the official account.

API Direct Call

The most flexible channel. Let business systems call Agents / Workflows directly:

curl -X POST https://api.evose.example.com/v1/agents/agent-12345/chat \
  -H "Authorization: Bearer pub_xxx" \
  -H "Content-Type: application/json" \
  -d '{"message": "hello", "user_id": "u-001"}'

→ API · Agent

Consistent Multi-Channel Experience

Regardless of which channel the user comes through:

The same Agent, the same prompts
The same user identity (linked by user_id)
The same conversation history
The same observability data

Next Steps

Model integration → Model providers
Configure credentials → Credentials

Integration · Channels

On this page