Integrations
Connect Keva to your existing tools and platforms
Keva lists 842 unique, risk-classified catalogued actions across 15 platform catalogues. This catalogue is not runtime availability: WordPress is the only self-serve setup surface; the other 14 catalogues are unavailable for this release, and platform effects are currently suspended.
Integration Types
Platform Connectors
E-commerce, DevOps, infrastructure, and business tools
CRM Sync
Local Salesforce and HubSpot sync paths; customer setup is not available in this release
Omnichannel
Support customers on Slack, Teams, SMS, and more
How Connectors Work
The diagram below is target architecture. Current platform execution and reply delivery stop before provider effects.
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Ticket │────▶│ Keva AI │────▶│ Policy │────▶│ Suspended │
│ Received │ │ Proposes │ │ Admission │ │ Before API │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │
▼ ▼
┌─────────────┐ ┌─────────────┐
│ Reply Draft │ │ Catalogue │
│ No Delivery │ │ Metadata │
└─────────────┘ └─────────────┘Connector Catalogues
Keva has 842 catalogued actions across 15 catalogues. Counts below are inventory, not enabled or provider-verified actions:
E-commerce & Payments
| Platform | Actions | Use Cases |
|---|---|---|
| Shopify | 84 | Orders, customers, products, fulfillment |
| Stripe | 66 | Payments, subscriptions, refunds, invoices |
| WordPress | 205 | Catalogue only; platform actions are not available in this release |
CRM & Marketing
| Platform | Actions | Use Cases |
|---|---|---|
| Salesforce | 38 | Contacts, accounts, cases, leads |
| HubSpot | 49 | Contacts, companies, deals, tickets |
DevOps & Infrastructure
| Platform | Actions | Use Cases |
|---|---|---|
| GitHub | 65 | Issues, PRs, repos, actions |
| Vercel | 29 | Deployments, domains, env vars |
| Railway | 25 | Projects, services, deploys |
| Cloudflare | 62 | DNS, caching, security |
| AWS | 40 | EC2, S3, Lambda, CloudWatch |
| Docker | 30 | Containers, images, volumes |
| Kubernetes | 30 | Pods, deployments, services |
| Supabase | 31 | Database, auth, storage |
Communication & Project Management
| Platform | Actions | Use Cases |
|---|---|---|
| Slack | 41 | Messages, channels, users |
| Jira | 47 | Issues, projects, sprints |
Setting Up a WordPress Connection
What AI Can Do
Security
Enterprise-Grade Security
Integrations use selected local security controls. This is not a statement of SOC 2 readiness, certification, operating effectiveness, or auditor approval.
Credential Storage
- Selected admitted credential envelopes use AES-256-GCM locally
- Credential fields are excluded from selected responses and audit metadata
- Only used for authorized actions
- Global credential re-encryption is currently suspended
Access Control
Current source has risk, approval, limit, and connector-management controls, but this page does not claim universal configured enforcement or enabled platform execution. Treat each connector action as unavailable until its setup, admission, provider effect, deployment, and customer-facing availability are recorded.
Audit Trail
Selected lifecycle and execution paths record content-minimized audit evidence:
- the action and affected resource
- the admitted actor when available
- categorical outcome metadata
Coverage is not universal, and raw credential or full request/response content is not an audit-log promise.