Jiandaoyun integration · Technical principles and dual role adaptation
API integration technology principles
In-depth analysis of HTTP/WebHook/OAuth, data formats and architecture patterns - providing division of responsibilities, joint debugging points and collaboration mechanisms from the dual perspectives of configuration personnel and developers .
30 seconds reading path
- is new to integration → Technical principles (protocol/authentication)
- Division of labor → Division of roles + collaboration mechanism
- wants to implement ERP → Kingdee · Yonyou special topic
1. Technical Principles: Third-party integrated core technology logic (dual role adaptation)
Integrate underlying protocols and technical support
Core communication protocol
- HTTP/HTTPS protocol: The most basic communication protocol, HTTPS is based on SSL/TLS encryption and is suitable for sensitive data scenarios.
- MQTT protocol: lightweight publish/subscribe protocol, suitable for IoT devices and real-time data synchronization scenarios
- OPC UA protocol: exclusive protocol for industrial control systems, supporting the transmission of complex process parameters
- WebHook protocol: HTTP-based callback mechanism to achieve event-driven integration
Data format and parsing
- JSON format: lightweight key-value pair data format, the mainstream return format for third-party APIs
- XML format: tagged data format, mostly used in traditional ERP and customs systems
- Binary format: is suitable for synchronizing files such as attachments and pictures.
Dual role application perspective
Identity Authentication and Security Mechanism Principles
Core authentication method
-
AppID/Secret authentication:
The third-party platform distributes unique identifiers and keys, and verifies the legitimacy of requests through key calculation signatures.
-
OAuth2.0 authentication:
Authorization code mode, suitable for scenarios that require user authorization, such as WeCom organizational structure synchronization
-
IP whitelist + key authentication:
The two-factor authentication mechanism used in high-security scenarios only allows access from specified IPs.
Data security protection
-
signature verification:
Generate a signature string through hash calculation to verify that the data has not been tampered with
-
Data encryption:
Sensitive data needs to be encrypted before transmission. Symmetric encryption is suitable for large amounts of data.
-
Principle of least privilege:
Only apply for necessary permissions during integration to reduce security risks from the permission design level.
Integrated architectural patterns and adaptation logic
One-way vs. two-way integration
The data is from the third-party system→Jiandaoyun or Jiandaoyun→the third-party system, with a simple architecture
For two-way data synchronization, a data consistency mechanism needs to be designed to avoid data conflicts.
No-code/low-code integration architecture
Configuration personnel take the lead, the bottom layer encapsulates protocols and authentication logic, and builds the process through drag and drop.
Developer-led, customized integration is achieved through code extension, and then encapsulated into a configuration interface
2. Basic Cognition: Core Responsibilities and Integration Principles of Configuration and Developers
Dual-role division of responsibilities and ability requirements
Configurator (low-code operator)
Based on the Jiandaoyun visual interface, complete basic integration, data mapping, and process configuration of third-party platforms without writing code.
Familiar with Jiandaoyun form/intelligent assistant/dashboard functions, and understand the basic authorization process of third-party platforms
Mainstream office platform integration, simple data synchronization, standardized API configuration, and basic attachment storage synchronization
Developer (low-code extender)
Responsible for non-standardized third-party integration, API custom development, and code-level expansion to support deep integration requirements that cannot be achieved by configuration personnel
Master JSON/XML data format, HTTP/HTTPS protocol, API signature verification logic, and be familiar with at least one programming language
ERP system integration, IoT device data docking, high security level integration, complex logic automation
Dual role collaboration mechanism
Develop and evaluate feasibility, configure and sort out business needs, and jointly formulate plans
Configuration completes visual operations, and development provides API docking code support
Configuration and troubleshooting basic issues, development and troubleshooting technical issues, forming a collaborative closed loop
Core principles and adaptation scenarios for third-party integration
core principles
-
Principle of least privilege:
When integrating third-party platforms, apply for the minimum necessary permissions to reduce data security risks.
-
Dual role adaptation principle:
Prioritize integration through configuration visualization, and then let developers intervene when it is not possible.
-
Principle of knowing everything about exceptions:
Development needs to add interface timeout retry, data verification and other mechanisms, and configuration needs to set synchronization failure reminders.
-
Reusability principle:
Configuration templates and code snippets are archived in a unified manner to form reusable assets.
Third-party integration classification
| Third party type | dominant role | core scene |
|---|---|---|
| Office collaboration | Configuration Dominant | Login-free access and organizational structure synchronization |
| Business system class | Development-led | Two-way data synchronization and business process linkage |
| E-commerce logistics | Configuration + Development | Order synchronization, waybill generation |
| Tool API | Collaborative work | Location, payment callback |
3. Core Skills: Practical Combination of Two-way Data Interaction (implemented in different role scenarios)
HTTP request node practice: configuration visualization vs development customization
Scenario 1: standardized message push (led by configuration personnel)
After-sales work order submission → WeCom customer service group notification, completed through Jiandaoyun visual configuration
- • Add an HTTP request node to the smart assistant
- • Select the POST method and fill in the Webhook address
- • Visually edit JSON request body
- • Direct selection of field variables
Scenario 2: push with signature verification (developer-led + configuration implementation)
Pushing work order data to a third-party business system requires API signature verification.
- • Develop and write signature generation scripts
- • Calculate timestamp + key encryption signature
- • Configure and fill in the parameters provided by the development
- • Joint debugging and optimization scripts
External data synchronization practice: third-party system→Jiandaoyun (multiple data source extension)
FeishuDocumentExcel
Configurator-led, field mapping skills
SQL Server database
Development-led, simplified cloud process configuration
金蝶K3 WISE
Development-led, deep integration
KingdeeK3 WISE deep integration practice
Actual scenario: Manufacturing customers synchronize KingdeeERP purchase order data to Jiandaoyun for workshop production scheduling
- • Connect to KingdeeERP purchase order query interface
- • Complete identity authentication (AppID/Secret)
- • Write interface call scripts
- • Handle data structure splitting
- • Verify data synchronization effect in Jiandaoyun
- • Optimize form field display
- • Set data sync reminders
- • Assist with testing and verification
4. Advanced expansion: practical implementation of no-code/low-code integration by role
Financial scenario: Kingdee/Yonyou+Jiandaoyun data interoperability (configuration-based)
Actual combat scenario
Financial personnel of small and medium-sized enterprises enter expense reimbursement forms through Jiandaoyun, and automatically synchronize to Kingdee/YonyouERP to generate vouchers. Financial data in ERP are synchronized to the Jiandaoyun dashboard to realize financial data visualization.
- • Connect to Kingdee/Yonyou voucher creation/financial data query interface
- • Write data synchronization scripts
- • Process the mapping of expense reimbursement form fields and ERP voucher fields
- • Add data verification logic
- • Create expense reimbursement form
- • Call API interface through smart assistant
- • Design financial dashboards and synchronize ERP revenue and expense data
- • Implement visual presentation
core value
Reimbursement forms are automatically converted into ERP vouchers, reducing manual entry.
Centralized display of financial data to facilitate decision-making analysis
ERP data is synchronized to Jiandaoyun in real time to maintain data consistency
Manufacturing scenario: IoT equipment + Jiandaoyun real-time monitoring (development leadership + configuration implementation)
Multi-protocol adaptation access
Workshop machine tools, smart sensors, lightweight data packets enable low-bandwidth, low-latency transmission
Industrial control systems such as PLC and SCADA directly capture the underlying data of the control system.
Simple sensor, low cost, non-real-time requirements
Warehouses, outdoor production lines, long-distance low power consumption scenarios
Dual roles coordinated landing
- • Technical implementation of the entire process of protocol docking, data analysis and API push
- • Provide interface call logs to facilitate troubleshooting
- • Data cleaning and anomaly filtering
- • Device monitoring form creation and field mapping
- • Real-time dashboard design and early warning rule configuration
- • WeCom notifications are pushed to maintenance personnel
5. Support and Guarantee: Dual-role Tools and Problem-Solving System
Role-based practical toolkit (direct link)
| Tool type | Tool name | Applicable roles | use | Official link |
|---|---|---|---|---|
| Office platform testing | WeChat public platform test account | configuration personnel | Test the integration function when there is no authentication service account | visited |
| Interface debugging | Postman | Development-led | HTTP request debugging, Webhook validity verification | visited |
| Open platform debugging | WeComAPI debugging tool | Developer | Group robot/Webhook testing, API call verification | visited |
| No code process | JiJianYun free version | Configuration Dominant | Codeless process construction and cross-platform data synchronization | visited |
| Code editing | VS Code | Developer | API script writing, data processing logic development | visited |
| Data format | JSON online verification tool | Collaborative use | JSON format verification, data structure beautification | visited |
| ERP docking | Kingdee open platform developer tools | Developer | KingdeeERP interface debugging and authorization verification | visited |
Kingdee/Yonyou product line docking actual scenario
Kingdee Galaxy accounts receivable/voucher interface practice
Jiandaoyun receivables registration form → Kingdee Galaxy receivables form generation → payment write-off synchronization (adapted to the management of foreign currency receivables of foreign trade enterprises), Jiandaoyun payables application form → Kingdee payables form creation → payment offset linkage to clarify the data flow node.
Jiandaoyun Expense Reimbursement Form/Purchase Requisition Form→Kingdee Galaxy automatically generates accounting vouchers (split by subject) and writes the voucher review status back to Jiandaoyun (avoiding duplication of documents), adapting to the financial automation needs of small and medium-sized enterprises.
Including the troubleshooting logic and solutions for typical problems such as "Failed to generate receivable note, the corresponding unit does not exist", "Failed to generate voucher, no operation authority for the account".
Yonyou product line docking practice
Jiandaoyun foreign trade order → U8 receivable note is generated (automatically brings out the foreign currency amount and exchange rate), and U8 receipt note is reviewed → Jiandaoyun order status is updated, which is suitable for current account management of manufacturing/foreign trade enterprises.
Jiandaoyun workshop expense note→U8 automatically generates manufacturing expense vouchers, and Jiandaoyun sales receipt note→U8 generates payment vouchers. The voucher number is written back to Jiandaoyun to facilitate financial reconciliation.
It is suitable for multi-organization accounts receivable and payable management in medium-sized enterprises, and supports the allocation of account permissions by organization to avoid cross-organization data leakage.
Frequently Asked Questions Troubleshooting Manual (Positioning and Solving by Role)
Integration failure issues
Data anomaly issues
6. Advanced expansion: Practical combat of no-code/low-code integration by role (continued)
Office scenario: Attendance system + Jiandaoyun salary accounting (dual role collaboration)
Actual combat scenario
When customers use DingTalk attendance/WeCom attendance, they need to synchronize attendance data (number of attendance days, overtime hours, and days of leave) to Jiandaoyun to automatically calculate employee salaries (basic salary + overtime salary - deduction).
- • Connect to DingTalk/WeCom attendance API and write data export scripts
- • Obtain employee monthly attendance data and process data calculations
- • Synchronize the processed attendance data to the Jiandaoyun payroll accounting form
- • Set the salary calculation formula in the Jiandaoyun form (basic salary + overtime hours × overtime rate - leave deduction)
- • Set up the salary data approval process and synchronize it to financial personnel for issuance confirmation
- • Verify payroll accounting accuracy and optimize formula logic
core value
Automatically synchronize attendance data to reduce manual accounting errors
Accurate calculation of overtime pay and leave deductions to avoid human errors
The approval process ensures accurate salary disbursement
Foreign trade scenario: Customs single window + Jiandaoyun customs declaration process (development docking + configuration optimization)
Actual combat scenario
Foreign trade companies enter customs declaration information through Jiandaoyun and automatically synchronize it to the customs single window. After obtaining the customs declaration receipt, they update the Jiandaoyun process status to realize the full process tracking of customs declaration.
- • Connect to the customs single window "customs declaration declaration" and "receipt inquiry" interface
- • Complete data encryption and identity authentication
- • Write interface calling scripts to submit customs declaration information and receive receipts
- • Process the receipt data returned by the customs interface, extract key information and synchronize it to Jiandaoyun
- • Design customs declaration process and set status update rules for each node
- • Design a customs declaration status dashboard to display the progress of each customs declaration form
- • Verification process status update and dashboard display
Things to note
Developers need to strictly follow data encryption and permission control requirements
Configuration personnel need to ensure the accuracy of customs declaration information entry
Real-time update of the status of the entire customs declaration process
E-commerce scenario: Doudian/Taobao + Jiandaoyun order whole process (configuration automation + development and leak filling)
Actual combat scenario
E-commerce customers need to synchronize Doudian/Taobao orders to Jiandaoyun, automatically allocate shipping warehouses, generate logistics orders, and abnormal orders (such as out of stock, invalid addresses) trigger the manual intervention process.
- • Connect to Doudian/Taobao order API through Jijian Cloud and set order synchronization rules
- • Set warehouse allocation rules in Jiandaoyun and automatically generate logistics orders
- • Set up an abnormal order intervention process and update the order status after the processing is completed
- • Write abnormal order judgment scripts and connect to the inventory management system
- • Mark and push abnormal orders to Jiandaoyun
- • Simulate abnormal order scenarios and optimize the processing process
core value
Orders are automatically synchronized and warehouses are automatically allocated, reducing manual operations.
Automatically identify abnormal orders and trigger the manual intervention process
Logistics orders are automatically generated and order status is updated in real time.
Ready to start your integration journey?
Configuration personnel and developers can find the division of labor guide and implementation path here.