Run TypeScript

Description

Execute TypeScript code in the in-process isolated-vm sandbox (the same battle-tested engine as Run JavaScript: V8-level isolation, no filesystem/network/module access, memory cap and wall-clock timeout enforced by the isolate). TypeScript is transpiled with type-stripping only (no runtime type-check → <50ms compile latency even on 50KB scripts), so type annotations, interfaces, type aliases, enums and "as" casts are supported and simply vanish at runtime. Script globals: `input` (previous node JSON output), `vars` (persistent workflow variables), `ctx` (tenantId, runId, nodeId). The value you `return` becomes the node output (must be JSON-serializable). Use case: typed data transformations, typed business logic (tiered commissions, multi-field validation), input reshaping before an API call, proprietary customer algorithms written in TS. For CPU-heavy or scientific work use Run Python; for HTTP calls use HTTP Request.

⚙️ Configuration parameters

Fields shown in the editor when configuring the node. Generated directly from the NodeDefconfigFields.

💡 Configuration example

JSON snippet of the node as it appears in the workflow. Values are derived fromdefaultValue and from required parameters.

{
  "id": "node-action_run_ts-1",
  "defId": "action_run_ts",
  "label": "Run TypeScript",
  "config": {
    "code": "// input = output del nodo precedente\n// vars = workflow variables · ctx = { tenantId, runId, nodeId }\n\ninterface Item { amount?: number }\nconst items: Item[] = (input.items as Item[]) ?? [];\nconst total: number = items.reduce((s, x) => s + (x.amount ?? 0), 0);\nreturn { total, count: items.length };\n",
    "timeoutMs": 5000,
    "memoryLimitMb": 128
  }
}

🔗 Related nodes in the same category