Direct API / SDK
Best for teams building an AI feature or gateway into their own product.
Integrations
Connect Clariva at the request boundary before provider execution.
Clariva connects where your application, workflow system, or product feature would otherwise call an AI provider directly. Each integration path is scoped around one request boundary: source system, policy, proof surfaces, provider route, rejection behavior, and evidence requirements.
Starter Paths
Choose the closest connection model.
Use these starter paths to scope how Clariva connects to a workflow source before AI execution. Evaluation defines the entry point, policy template, provider route, audit scope, authentication approach, and deployment-readiness questions.
Deployment scope, credentials, retention, networking, support obligations, and any managed-control-plane responsibilities are confirmed during evaluation and written agreement.
Application entry points
Signed webhook
Best for routing structured workflow events through the deployed Clariva control layer for controlled evaluation.
Workflow systems
CRM workflow
Best for scoping account notes, customer summaries, sales context, and CRM-based AI use. Named-platform connector readiness is confirmed during integration review.
Support workflow
Best for scoping tickets, conversations, summaries, routing, and support quality review. Named-platform connector readiness is confirmed during integration review.
Internal assistant workflow
Best for scoping employee prompts, internal documents, customer context, or assistant requests before provider execution.
Embedded SaaS workflow
Best for product teams adding AI features where tenant, workspace, or user-generated content needs request-path control.
Custom application workflow
Best for internal tools, queues, webhooks, API gateways, or enterprise data paths that need workflow-specific review.
Control requirements
Provider-neutral routing, scoped during evaluation.
Clariva is designed to control the path to eligible provider routes, not to force a single model provider. A route can represent a customer-approved path to Bedrock, Azure OpenAI, Vertex AI, OpenAI, Anthropic, an internal model, or another approved provider path, subject to deployment and contract scope.
Connector and writeback controls require explicit scope.
For CRM, support, ticketing, workflow, or writeback scenarios, evaluation confirms the source system, authentication approach, allowed actions, policy requirements, evidence scope, and production readiness. Public website references should not be treated as connector availability guarantees.
Current Integration Coverage
Current integration coverage.
Clariva currently includes completed integration coverage for common customer workflow, CRM, knowledge, and communications systems. Evaluation confirms the source system, authentication approach, allowed actions, provider route, evidence scope, and deployment readiness for the selected workflow.
| Integration | Typical workflow |
|---|---|
| Zendesk | Support tickets, customer conversations, routing, and summarization workflows. |
| Salesforce | CRM notes, account context, sales workflows, and customer-record analysis. |
| HubSpot | Marketing, CRM, and customer communication workflows. |
| Notion | Internal knowledge, documents, pages, and team workspace context. |
| Twilio | Messaging, communication, notification, and customer interaction workflows. |
Integration coverage does not mean every customer deployment, writeback action, authentication pattern, marketplace listing, or production configuration is automatically available. Evaluation confirms the permitted actions, credentials model, data boundaries, and deployment obligations for each workflow.
Integration Review
What the intake captures.
A focused intake helps determine whether the workflow fits a standard path or requires additional enterprise planning.
Source system
Where the request starts and how the deployed control layer receives it.
Data classes
The types of sensitive text the workflow may contain.
Provider route
The model provider or provider family the workflow expects to use.
Review level
The security, privacy, compliance, or procurement review required before production.
Connection Path
Start with the integration closest to your workflow.
The demo form helps route your request to API/SDK, CRM, support, webhook, or Enterprise Control.
For technical integration details, see the Technical Overview →