Define Workflows

Updated 3 days ago • October 4, 2026

The core contract lives in @kortyx/core and is exposed through kortyx.

Good to know: If you want the mental model for what a node receives and returns, start with Nodes before using this page as the workflow shape reference.

TypeScript workflow (recommended)

import { defineWorkflow } from "kortyx";
import { google } from "@/lib/providers";
import { classifyNode } from "@/nodes/classify.node";
import { answerNode } from "@/nodes/answer.node";

export const supportWorkflow = defineWorkflow({
  id: "support",
  version: "1.0.0",
  description: "Simple support flow",
  nodes: {
    classify: {
      run: classifyNode,
      params: { model: google("gemini-2.5-flash") },
      behavior: {
        retry: { maxAttempts: 2, delayMs: 200 },
      },
    },
    answer: {
      run: answerNode,
      params: {},
    },
  },
  edges: [
    ["__start__", "classify"],
    ["classify", "answer", { when: "support.answer" }],
    ["answer", "__end__"],
  ],
});

Callable workflows

A workflow called by useWorkflow(...) declares inputSchema and outputSchema. Its last node returns ordinary data and reaches __end__; the runtime validates accumulated child data and returns it to the caller. Existing root workflows can omit these schemas.

Calls live in node code or custom hooks. Register both workflows with the agent; no special call edge or return node is required. See Call Child Workflows for typed definitions, string IDs, and interrupts.

Node return shape

Nodes return a subset of NodeResult. See Nodes for the full return contract and how returned data is passed to the next node.

Important fields in practice:

data: merged into runtime state and forwarded as future input
ui.message: emitted as a final message event
ui.structured: emitted as structured-data
condition / intent: used for conditional edge routing
transitionTo: triggers workflow handoff

Node behavior currently implemented

From WorkflowNodeBehavior and runtime code:

behavior.retry.maxAttempts
behavior.retry.delayMs
behavior.checkpoint

Note: onError.mode exists in schema types but is not currently applied by the execution graph compiler.

Validation

You can validate directly: