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.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
| Layer | What it does |
|---|---|
| Codika Dashboard | Web application where users manage organizations, projects, integrations, and processes. |
| codika-helper CLI | Command-line tool (npm install -g @codika-io/helper-sdk) 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
- The CLI validates the folder structure, config exports, and workflow patterns
- Workflows are packaged and sent to the Codika platform API
- The platform creates versioned deployment records and a process instance for the user
- Workflows are deployed to n8n with all placeholders replaced with real values
- 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)
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 |