Integrate Chatwork with Jinba

Yes. Jinba is built for on-premise and private cloud deployment, which means the Chatwork integration runs entirely within your own infrastructure. Sensitive documents, communications, and workflow data do not pass through Jinba's public cloud. This is a core requirement for banks, insurance companies, and other regulated enterprises operating in air-gapped or controlled environments.

No. Jinba supports private model hosting via AWS Bedrock, Azure AI, or self-hosted models. Any AI processing triggered through a Chatwork workflow uses your organization's privately hosted model, not a public LLM endpoint. This ensures that sensitive financial or customer data shared via Chatwork remains within your security perimeter at all times.

Every workflow execution initiated through Chatwork is recorded in Jinba's audit log, capturing who triggered the workflow, what inputs were provided, and what outputs were produced at each step. These logs are structured for regulatory review and internal audits, satisfying the auditability requirements common in banking, insurance, and other regulated industries.

Yes. Jinba enforces role-based access control (RBAC) and integrates with SSO and Active Directory. Workflows shared across the team are governed by permissions set in Jinba Flow, so only authorized users can invoke specific automations from Chatwork. This separates who can build workflows from who can run them, a key governance requirement for regulated operations teams.

Regulated enterprises commonly use the Chatwork integration to trigger KYC document intake, contract review, compliance checks, and loan review coordination. Jinba's deterministic workflow architecture (80% rule-based) ensures consistent, auditable outputs for these processes. Non-technical business users can invoke these workflows directly from Chatwork via auto-generated input forms, without needing access to the underlying workflow tooling.