Skip to main content

​
Why build a custom dashboard?

Codika deploys your workflows as stable HTTP endpoints with credential isolation and execution tracking. You can trigger these endpoints from any frontend — not just the Codika dashboard. This means you can build a custom app that:
  • Triggers your workflows from your own UI
  • Displays results in your own format
  • Manages its own users and data
  • Talks to your own database alongside Codika

​
Architecture

Your App (SvelteKit, Next.js, any framework)
  → Your API routes (server-side, holds API key)
    → Codika Public API (trigger + poll)
      → n8n workflow (business logic, integrations)
        → Result returned to your app
What Codika provides:
  • Stable HTTP endpoints per workflow (don’t change across versions)
  • Credential isolation (your app never sees integration tokens)
  • Execution tracking (trigger, poll status, get results)
  • Dev/prod environments with separate instance IDs and API keys
  • Secured n8n endpoints (workflows are only callable through the Codika API, not directly)
What you build:
  • The frontend (UI, forms, data display)
  • Your own database (users, audit logs, app-specific data)
  • Server-side API routes that proxy to Codika (keeps API key private)
  • Business logic around the workflow results

​
The integration is simple

Your app only needs three things from Codika:
WhatHow
Trigger a workflowPOST triggerWebhookPublic/{processInstanceId}/{workflowId} with X-API-Key header
Poll for resultsGET getExecutionStatusPublic/{processInstanceId}/{executionId} with X-API-Key header
Know what’s availableAgent skills describe each endpoint’s input/output (optional but helpful)
That’s it. Two endpoints, one API key, and you can build anything on top.

​
Next steps

Authentication

Understand the two API key types and how to store them securely.

Trigger & Poll

The core pattern: trigger a workflow, poll for results, parse the output.

Environments

Switch between dev and prod with separate instance IDs and API keys.

Common Patterns

Error handling, retry logic, audit trails, and security best practices.