Platform Connector Catalogue
Connector inventory and current setup availability for 15 platform catalogues
Keva lists 842 unique, risk-classified connector actions across 15 platform catalogues. This is inventory, not enabled behavior. Platform-action execution is globally suspended; provider setup, rollback, deployment, and customer-facing availability remain separate requirements.
Connector Catalogues
E-commerce & Payments
| Platform | Actions | Primary Use |
|---|---|---|
| Shopify | 84 | Order management, customer data |
| Stripe | 66 | Payments, subscriptions, refunds |
DevOps & Hosting
| Platform | Actions | Primary Use |
|---|---|---|
| GitHub | 65 | Issue tracking, code, deployments |
| Vercel | 29 | Deployment status, logs |
| Railway | 25 | App management, deployments |
Infrastructure
| Platform | Actions | Primary Use |
|---|---|---|
| AWS | 40 | Cloud resources, status |
| Cloudflare | 62 | DNS, security, performance |
| Docker | 30 | Container management |
| Kubernetes | 30 | Orchestration |
Business Tools
| Platform | Actions | Primary Use |
|---|---|---|
| Jira | 47 | Issue tracking, projects |
| Slack | 41 | Team communication |
| HubSpot | 49 | CRM, marketing |
| Salesforce | 38 | CRM, sales |
CMS & Backend
| Platform | Actions | Primary Use |
|---|---|---|
| WordPress | 205 | Catalogue only; platform actions are not available in this release |
| Supabase | 31 | Database, auth |
Connecting a Platform
Step 1: Navigate to Integrations
Go to the top-level Integrations page.
Step 2: Find the Platform
WordPress is the only self-serve setup surface for this release. The other 14 catalogues are unavailable; do not supply credentials.
Step 3: Click Connect
Use the WordPress plugin plus Bridge token path only. Do not supply credentials for any other catalogue.
Step 4: Configure Permissions
Stored connected state is administrative metadata, not live health or confirmation that
the platform ran.
Step 5: Test Connection
Where a health control exists, its result is a scoped diagnostic rather than confirmation that every catalogued action works.
Managing Connectors
Use the top-level Integrations page. Available view, edit, health, and delete controls vary by platform. Stored status and timestamps are administrative evidence, not provider health or confirmation that the platform ran.
Deleting a supported Keva connector record does not prove that a provider token, browser session, cached credential, webhook, or other provider-side access has been revoked. Revoke provider-issued credentials at the provider separately.
How AI Uses Connectors
Automatic Context
The intended read path is designed to:
- Identify relevant platforms (e.g., customer mentions order)
- Query connected platforms for data
- Include information in response
Action Execution
The intended mutation path is designed to:
- Determine an action is needed
- Check permissions and limits
- acquire the required authority and approval
- execute only after the global suspension is deliberately lifted
- check the provider effect separately before reporting success
Example Flow
This is a target flow, not a current customer flow: a refund request would require current connector setup, exact ticket and tenant custody, policy and approval admission, durable provider-start identity, provider receipt, a separate result check, and a separately admitted customer response. Platform execution and reply delivery are currently suspended.
Security & Permissions
Credential Security
- Selected admitted connector credential fields use AES-256-GCM envelopes locally
- Selected responses and audit projections exclude credential values; universal log, error, provider, and historical coverage are not available as universal customer-facing coverage
- Scoped to minimum required permissions
Action Control
Risk metadata, approval policy, action limits, and connector state are inputs to the intended admission model. The current global suspension overrides them.
Audit Logging
Selected connector lifecycle and action paths record content-minimized evidence such as action/resource identity, admitted actor, and categorical outcome. Universal connector usage, data-access, credential-access, provider, and full-context logging is not confirmed as universal.
Troubleshooting
Use only the customer-reachable setup surfaces listed above. A stored connector row or successful health response does not make actions available. If a setup or health check fails, preserve the exact product error and avoid rotating or re-entering credentials until the platform-specific requirements have been reviewed.
Platform actions are expected not to run while the global suspension is active.
Rate Limits
Provider rate-limit handling varies by connector and is not confirmed as a universal configured behavior. Do not infer queueing, retry, or limit enforcement from catalogue metadata.
Need a New Connector?
Don't see your platform?
- Contact us with your request
- Tell us what platform and use case
- We'll evaluate and add to roadmap