Integrations
We review which data to bring in, how to connect existing systems, and who needs access.
- 01Source materialsDocuments · ERP · Email · Databases
- 02Connection requirementsData format · Access · Update frequency
- 03Apply to the workflowSearch · Review · Approve · Processing history
Environments to connect
This is not a list of included connectors. Connection feasibility and implementation scope depend on your environment.
Documents & files
Check supported formats and fields in PDFs, documents, and spreadsheets.
ERP & business systems
Identify which item, customer, and order data is needed and how to connect the existing system.
CRM & customer data
Review customer, inquiry, and follow-up data alongside access permissions.
Email & collaboration
Define feasible connections for incoming materials, notifications, reviews, and approvals.
Databases
Agree on data access methods, field meanings, permissions, and processing records.
Cloud & on-premises
Agree on deployment, managed environments, and operating responsibilities.
Frequently asked questions
Can you deploy in our environment?
The agreement defines deployment and management, whether SHINCHUK cloud, your cloud, or on-premises servers. We first verify environment requirements and implementation scope.
Does every new workflow incur a development fee?
Adding or configuring work with included capabilities within existing limits does not automatically create per-workflow development fees. Additional SHINCHUK development, increased usage, or new organizations, environments, and products follow separate terms.
Are AI results finalized automatically?
Human review and approval are defined according to the importance of the work. Models, data, evaluation criteria, and permitted actions are specified in the agreement.