Integrations
31 integration recipes, 18 data connectors, and 6 self-hosted inference-backend guides.
CortexDB ships 31 integration recipes and 18 data connectors across the AI ecosystem. Every
integration recipe is a thin adapter on top of the Python and TypeScript SDKs — copy, paste, swap in your
scope, ship. Every recipe works the same against a self-hosted server
(the recommended setup — point the client at http://localhost:3141) or the managed cloud; just change
the base URL. Data connectors ingest from third-party systems on a schedule, run self-hosted with the
cortexdb-sync CLI (recommended) or as a managed worker.
The 6 inference-backend pages are deployment guides for self-hosted and enterprise instances — they
configure the model router used by /v1/answer and the Understanding synthesizer, and are listed
separately and excluded from the integration count.
| Category | Count | Tier |
|---|---|---|
| Agent frameworks | 22 | Free + paid (SDK recipes — same code on every tier) |
| Orchestration | 6 | Free + paid (SDK recipes) |
| No-code platforms | 3 | Free + paid (HTTP/SDK recipes) |
| Data connectors | 18 | Managed sync workers or self-hosted (cortexdb-sync) |
| Inference backends | 6 | Deployment-side — used by /v1/answer + synthesizer |
Agent frameworks
22 frameworks. Every page is a self-contained recipe — a memory adapter, a retriever class, or a tool
wrapper that talks to CortexDB via V1Client. Install the matching extra, e.g. pip install cortexdbai[langchain].
LangChain · LangGraph · LlamaIndex · CrewAI · AG2 (AutoGen) · AutoGen · Agno · DSPy · Smolagents · CAMEL-AI · PydanticAI · OpenAI Agents · Google ADK · Letta · BeeAI · NeMo Guardrails · Instructor · ControlFlow · Eliza OS · Hermes · OpenClaw · Mastra
Orchestration
Temporal · n8n · Prefect · Airflow · Zapier · Make.com
No-code platforms
Vercel AI SDK · Flowise · Dify
Inference backends
Server-side deployment guides — they configure which model CortexDB's /v1/answer route and Understanding
synthesizer call. Use these if you self-host or run an enterprise deployment.
Ollama · Groq · Together AI · Fireworks AI · vLLM · DeepInfra
These pages configure the answer lane (CORTEX_ANSWER_*), not just CORTEX_LLM_* (which is entity
extraction). Setting CORTEX_LLM_* alone leaves /v1/answer disabled (503 ANSWER_UNAVAILABLE) on a self-hosted
server. See each page.
Data connectors
18 third-party systems. A connector can run as a managed sync worker (provisioned from your account
dashboard) or self-hosted with the cortexdb-sync CLI — point it at your Slack workspace / GitHub org /
Jira project once and it continuously ingests into your scope as conversation / document experiences.
| System | Doc |
|---|---|
| Slack | /docs/connectors/slack |
| GitHub | /docs/connectors/github |
| GitLab | /docs/connectors/gitlab |
| Jira | /docs/connectors/jira |
| Freshdesk | /docs/connectors/freshdesk |
| tl;dv | /docs/connectors/tldv |
| Linear | /docs/connectors/linear |
| Confluence | /docs/connectors/confluence |
| Notion | /docs/connectors/notion |
| PagerDuty | /docs/connectors/pagerduty |
| Discord | /docs/connectors/discord |
| Microsoft Teams | /docs/connectors/teams |
| Google Workspace | /docs/connectors/google-workspace |
| Salesforce | /docs/connectors/salesforce |
| HubSpot | /docs/connectors/hubspot |
| Zendesk | /docs/connectors/zendesk |
| Intercom | /docs/connectors/intercom |
| ServiceNow | /docs/connectors/servicenow |
Self-hosting connectors yourself? See the Self-hosted connectors overview for the
cortexdb-sync CLI, credential precedence, --scope-template, and the serve webhook receiver.
Not in this list?
The Python, TypeScript, and REST interfaces work everywhere fetch does. If you have a framework,
orchestrator, or pipeline that isn't listed, the SDK/REST path works — and for a new managed connector,
contact the team.