WeCom
callback, message, user mapping
← All capabilities
Integrations / Channel-neutral Access
Channels can differ.Customer context, governance, and outcomes must remain continuous.
NexusClaw treats WeCom, Feishu, DingTalk, Web Chat, API, phone, and Mobile H5 as access channels—not separate AI products. After entry, every request returns to the same identity, routing, permission, execution, audit, and attribution chain.
Integration does not end with a 200 callback. The system must validate signature and workspace, map the real user, preserve conversation context, resolve routing, handle duplicates and failure, and hand off to people when needed.
Product UI · AI Access CenterNexusClaw Product UI
01 / Channel Entry
Not eight integration products—one extensible access contract
Current types span enterprise IM, web, API, and phone. A new channel needs credential metadata and an adapter, not a new customer truth, learning store, or audit system.
Feishu
event, encryption, user mapping
DingTalk
callback, bot, user mapping
Slack
bot integration type
Teams
bot integration type
Web Chat
web session and simulator
Web API
controlled programmatic entry
Phone Agent
phone and voice entry
Two surfaces with different ownership
01
Workspace default IM gateway
Configure WeCom, Feishu, and DingTalk default Agent, session timeout, context size, and sensitive-data policy.
02
AI Access Center
Manage channel-neutral bots, group bindings, Smart Routing, dispatcher, and sanitized access records.
02 / Signature, Identity & Routing
Before a message reaches the model, prove where it came from, whom it represents, and where it may go
Headless callbacks pass platform protocol validation and bind to the current workspace. External user mapping and session state connect the real caller; Smart Routing selects an employee or dispatcher by explicit priority.
Protocol validation
Verify channel signature, token, or encrypted event and reject an unproven source.
Workspace binding
Callback, config, mapping, and session must remain in one workspace.
User mapping
Map the external platform user to platform identity instead of sharing an anonymous principal.
Sanitized evidence
Access records keep direction, route, target, status, and latency—not message body or credential.
Smart Routing order
01 · Requested employee
explicit employee
02 · Exact group
match target group
03 · Default dispatcher
unique default
04 · Smart endpoint
priority match
05 · Dispatcher fallback
controlled fallback
Credential storage
AES-256-GCM · configured fields only
Session evidence
status, target, latency
Sensitive boundary
no body or secret
03 / Conversation & Mobile Continuity
Leaving desktop does not leave the customer record or execution chain
Mobile H5 is not a read-only thumbnail. Workbench, cross-object search, notifications, business objects, and Agent voice entry share the same workspace and business data. WeCom and DingTalk WebViews use a common mobile adapter for scan, location, image, and push capabilities.
Product UI · Mobile H5 workbenchNexusClaw Product UI
Product UI · Mobile H5 global searchNexusClaw Product UI
Text, voice, and video enter the same Agent workbench
Voice/text and video switching does not create another Agent. Employee identity, long-term memory, permissions, tools, approval, and audit remain consistent; mobile can use text or push-to-talk in the same conversation.
Product UI · AI employee voice/video workbenchNexusClaw Product UI
A channel delivers demand; it does not own customer truth
Channel adapter
Parse platform event
Identity and session
Map the real caller
Smart Routing
Select employee or dispatcher
Controlled execution
Permission, tools, approval
Audit and attribution
Preserve outcome evidence
04 / Failure, Retry & Handoff
Integration failure must be diagnosable, retryable, and handoff-ready
Webhook timeout, signature failure, or upstream outage is not swallowed. The dead-letter queue retains event type, error, status code, retry count, and time, distinguishing retryable failures from configuration defects.
01
401 · signature failed
Repair secret or signing configuration; blind retry will not succeed.
02
504 · upstream timeout
After network and downstream health recover, retry by policy.
03
Duplicate delivery
Use platform event identity and idempotency boundaries to prevent duplicate actions.
04
Human handoff
An active session can move to a person with a recorded reason.
Product UI · Webhook dead-letter queueNexusClaw Product UI
Customer Evaluation Checklist
Deliberately causing errors is more valuable than sending one successful message
01
Forge a signature or use a wrong token
Confirm rejection before the request enters session or Agent context.
02
Deliver the same event twice
Confirm no duplicate business action or reply.
03
Continue one customer task across channels
Check record, permission, execution, and audit continuity.
04
Trigger timeout and human handoff
Confirm a diagnosable failure record and explicit transfer to a person.
Current capability boundary
Channel support depends on the target platform application, permissions, callback network, and credentials. This page does not imply channel-vendor certification. Slack, Teams, Web Chat, API, and Phone Agent are unified integration types; delivery depth is accepted per target platform and project scope.
Bring your target channels, identity model, and failure scenarios
We will map callback entry, signature and workspace binding, user mapping, Smart Routing, mobile continuity, dead-letter retry, and human-handoff acceptance.