> For the complete documentation index, see [llms.txt](https://docs.krnl.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krnl.xyz/enterprise-integration/overview.md).

# Overview

## Enterprise Integrations

KRNL provides pre-built integration patterns for popular enterprise platforms, enabling you to add cryptographic verification, audit trails, and automated workflows to your existing systems without replacing your infrastructure.

### Available Integrations

| Platform                                               | Capability                                                                                   |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------- |
| [Salesforce](/enterprise-integration/salesforce.md)    | Secure document management with identity-bound watermarking and cryptographic fingerprinting |
| [HubSpot](/enterprise-integration/hubspot.md)          | Secure document management with identity-bound watermarking and cryptographic fingerprinting |
| [Custom](/enterprise-integration/custom-connectors.md) | Build your own connector using the KRNL SDK and Studio                                       |

### Common Integration Patterns

All enterprise integrations follow the same underlying pattern:

1. **Connect** — Authenticate to your platform via standard OAuth or API keys
2. **Define** — Map platform events (record updates, file uploads, stage changes) to KRNL workflow triggers
3. **Execute** — KRNL runs the workflow in a sandboxed environment with full attestation
4. **Verify** — Results are cryptographically signed and delivered back to your platform
5. **Audit** — Every action is logged with an immutable proof for compliance reporting

### Security Considerations

* Platform credentials are resolved at runtime by your Attestor, never stored in workflow definitions
* All platform API calls are intercepted, logged, and signed by the Attestor
* Watermarks, fingerprints, and proofs are generated server-side, not client-side
* Delegated accounts ensure user wallets are never exposed to integration logic