Can a custom system integrate with WeCom, DingTalk, Feishu, ERP, and CRM?
Yes, but a brand name alone does not prove an integration is available. Confirm the client's product version, official APIs, obtainable permissions, and source of truth for each field. Prefer official APIs with one-way or event synchronization. Allow two-way writes only when every field has one owner and a documented conflict rule.
WeCom, DingTalk, and Feishu are collaboration entry points; ERP, CRM, and finance systems hold business facts. The former commonly provide single sign-on, directory, messages, approvals, and workbench embedding. The latter exchange customers, products, orders, stock, payments, and invoices. Wavesteam does not promise unrestricted two-way synchronization because it lets both systems rewrite the same data.
When decomposing features, data, and acceptance scenarios, also compare Can data from a login-only system with no export be automated into Excel or reports?; the linked guidance adds context that should be considered in the same decision.
| Method | Suitable situation | Advantage | Risk | Recommendation |
|---|---|---|---|---|
| CSV/Excel exchange | Infrequent work, old system without API, early field test | Quick and reviewable | Delay, duplicates, format errors | Transitional with batch logs |
| Official API one-way | One clear fact owner | Simple boundaries, retries, reconciliation | Limits, authorization, version changes | Default for most integration |
| Webhook/events | State changes need low delay | Less polling | Loss, duplication, reordering | Combine with periodic reconciliation |
| Limited two-way | Systems own different fields | Completes a workflow | Conflicts, loops, complex permissions | Use after a field-ownership map |
Feishu Open Platform documents directory, messaging, approval, and documents. WeCom custom, provider-built, and third-party applications can have different directory scope and may require member authorization; verify in the WeCom Developer Center. DingTalk permissions depend on application type in the DingTalk Open Platform. A client administrator creates the application, visibility, callback, and keys; a developer's public account should not own it permanently.
ERP/CRM access varies by vendor, edition, deployment, and licence. SaaS may charge for open-platform access; an old local version may expose only files or database; a custom system may lack field documentation. Direct database access can bypass rules and break on upgrade and should be read-only or controlled, officially supported, and change-managed. Browser scraping or private-client APIs are last resorts requiring authorization.
Create a system and field responsibility map. HR owns employment and department while WeCom consumes a directory; ERP owns products and stock; CRM owns leads and follow-up; the new system owns its specialist tickets. For every field specify direction, frequency, identifier, units, timezone, nulls, deletion, and conflict. A CRM “customer” may be a contact while an ERP “customer” is a legal invoice entity.
Use the platform's OAuth or authorization, store secrets securely, verify callbacks and prevent replay, include event IDs/idempotency, send failures to retry and human queues, and run reconciliation. Logs retain source version, target ID, response, and business reason, not only success/failure. OpenAPI can formalize external contracts behind an adaptor layer.
Integrate in stages. Start with one valuable path, such as an ERP ticket entering the new system, status returning to ERP, and WeCom receiving a notification. Test identity, fields, duplicates, limits, and revoked access before adding directory or approvals. Technical access does not justify synchronizing every employee phone, customer record, and historical order.
Acceptance covers initial full load, increments, edits, deletion or departure, duplicates, ordering, timeouts, expired tokens, limits, missing fields, and target outage. Measure end-to-end delay, backlog, reconciliation differences, repair time, and unauthorized requests. Wavesteam's factory management case shows related integration direction; each exact version still requires technical verification.