Skip to main content

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 CaseTriggerWhat it does
Email attachment organizerNew email arrivesSaves attachments to Google Drive, logs to Sheets
Daily inbox intelligenceCron schedule (8 AM)Categorizes unread emails with Claude, marks newsletters as read
CRM funnel reporterSchedule + manual HTTPPulls Folk CRM pipeline data, posts summary to Slack
Proposal generatorUser submits formSearches similar docs via RAG, generates PDF proposal with Claude
Web search toolHTTP webhookRuns 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:
LayerWhat it does
Codika DashboardWeb application where users manage organizations, projects, integrations, and processes.
codika-helper CLICommand-line tool (npm install -g @codika-io/helper-sdk) for scaffolding, validating, and deploying use cases.
Codika Platform APIBackend that handles deployment orchestration, credential resolution, version management, and workflow execution.

How deployment works

Use case folder (config.ts + workflows/*.json)
  → codika-helper verify (validation)
  → codika-helper 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

ConceptDefinition
Use caseA folder containing config.ts and workflows/ that defines a deployable automation
ProcessThe public, discoverable representation of a deployed use case
Process instanceA user’s personal installation of a process with isolated credentials and data
PlaceholderA template token (e.g., {{FLEXCRED_ANTHROPIC_ID_DERCXELF}}) replaced at deployment with real values
Codika nodesCustom n8n nodes (Init, Submit Result, Report Error) that integrate workflows with the platform
TriggerHow a workflow starts: HTTP webhook, cron schedule, service event, or sub-workflow call

Next steps