> ## Documentation Index > Fetch the complete documentation index at: https://doc.codika.io/llms.txt > Use this file to discover all available pages before exploring further. # What is Codika? > A multi-tenant SaaS platform for building, deploying, and managing n8n workflow automations with AI-powered orchestration ## Overview Codika is a platform that turns natural language descriptions into production-ready n8n workflow automations. It handles the full lifecycle: building workflows, deploying them to n8n, managing credentials, tracking executions, and distributing automations across organizations. The platform solves a specific problem: **n8n workflows are powerful but hard to productize**. Codika wraps n8n with multi-tenant deployment, credential isolation, version management, and a deployment pipeline that makes workflows installable and shareable. ## Built for humans AND agents Codika lets you build **dedicated APIs that contain the exact actions you want your agents to perform** — and completely decouples the authentication layer from agent usage. Agents get capabilities, not credentials. **How it works:** You build workflows that perform actions (search a CRM, generate a proposal, send a WhatsApp message). Codika deploys them as HTTP endpoints. You then create **agent skills** — documentation files that explain what each endpoint does, what input it expects, and what output it returns. Agents download these skills and know exactly how to use your APIs. **Why this matters:** Connecting agents to existing tools today means giving them OAuth tokens, API keys, and passwords — a security and operational nightmare. Codika inverts this. You connect your integrations once to the platform. The platform stores and manages all credentials. When an agent triggers a workflow, Codika injects the right credentials at runtime. The agent only ever holds a single Codika API key that grants access to the actions you've defined — nothing more. * **You define the agent's tool stack** — each workflow is an action, each skill documents it * **Agents call actions, not APIs** — `codika trigger send-message` instead of raw Twilio/Salesforce/Google calls * **One key to revoke** — disable the process instance and the agent loses access to everything, no credential rotation needed * **Same endpoints, two audiences** — the dashboard serves humans, the skills serve agents, the workflows power both ## What you can build A **use case** is Codika's fundamental deployment unit. It packages one or more n8n workflows with configuration, schemas, and metadata into a single deployable artifact. Examples of what use cases do: | Use Case | Trigger | What it does | | -------------------------- | ---------------------- | ----------------------------------------------------------------- | | Email attachment organizer | New email arrives | Saves attachments to Google Drive, logs to Sheets | | Daily inbox intelligence | Cron schedule (8 AM) | Categorizes unread emails with Claude, marks newsletters as read | | CRM funnel reporter | Schedule + manual HTTP | Pulls Folk CRM pipeline data, posts summary to Slack | | Proposal generator | User submits form | Searches similar docs via RAG, generates PDF proposal with Claude | | Web search tool | HTTP webhook | Runs Tavily search, returns formatted results | ## Architecture ``` User request (form, schedule, webhook, service event) → Codika platform (credential resolution, execution tracking) → n8n workflow (business logic, API calls, AI processing) → Results returned to user (structured output, files, notifications) ``` The system has three layers: | Layer | What it does | | ----------------------- | ----------------------------------------------------------------------------------------------------------------- | | **Codika Dashboard** | Web application where users manage organizations, projects, integrations, and processes. | | **codika CLI** | Command-line tool (`npm install -g codika`) for scaffolding, validating, and deploying use cases. | | **Codika Platform API** | Backend that handles deployment orchestration, credential resolution, version management, and workflow execution. | ## How deployment works ``` Use case folder (config.ts + workflows/*.json) → codika verify (validation) → codika deploy (packaging + API call) → Codika Platform (version management, deployment records) → n8n (placeholder replacement, credential injection, workflow creation) → Live automation (accessible via triggers) ``` When you deploy a use case: 1. The CLI validates the folder structure, config exports, and workflow patterns 2. Workflows are packaged and sent to the Codika platform API 3. The platform creates versioned deployment records and a process instance for the user 4. Workflows are deployed to n8n with all placeholders replaced with real values 5. The automation is live and can be triggered via HTTP, schedule, or service events ## Multi-tenancy model Every deployment is isolated per user. When a user installs a process, they get their own **process instance** with: * Isolated credentials (their own OAuth tokens, API keys) * Personal deployment parameters (configured at install time) * Independent execution tracking * Separate activation controls (pause, archive, reactivate) ``` Organization ├── Projects (scoped workspaces) ├── Integrations (OAuth connections: Gmail, Slack, Drive, etc.) ├── Members (roles: owner, member, viewer) └── Process Instances (deployed automations, one per user) ``` ## Key concepts | Concept | Definition | | -------------------- | ----------------------------------------------------------------------------------------------------------- | | **Use case** | A folder containing `config.ts` and `workflows/` that defines a deployable automation | | **Process** | The public, discoverable representation of a deployed use case | | **Process instance** | A user's personal installation of a process with isolated credentials and data | | **Placeholder** | A template token (e.g., `{{FLEXCRED_ANTHROPIC_ID_DERCXELF}}`) replaced at deployment with real values | | **Codika nodes** | Custom n8n nodes (Init, Submit Result, Report Error) that integrate workflows with the platform | | **Trigger** | How a workflow starts: HTTP webhook, cron schedule, service event, or sub-workflow call | | **Agent skill** | A Claude-compatible documentation file (`SKILL.md`) that describes how to interact with a deployed workflow | ## Next steps Understand why Codika exists and what it adds on top of n8n. Install the CLI and deploy your first use case in minutes. Add Codika skills and builder agents to Claude Code, Cursor, or any Open-Plugin-compatible agent. Understand how use cases are organized and configured. Full reference for all codika CLI commands. Real-world use case examples with complete code. Let AI agents create use cases from your business requirements. Make your workflows discoverable and usable by AI agents. Build a custom frontend on top of your deployed workflows.