Output SDK Workflow Orchestrator FAQs

Question 1

Can I use the standard Zod library for schemas?

Accepted Answer

No, you must import 'z' directly from '@outputai/core'. This ensures the schemas are compatible with the Output SDK's internal validation and execution engine.

Question 2

Why must the workflow function be deterministic?

Accepted Answer

Determinism ensures that the orchestration logic is predictable and can be safely re-run by the SDK without unexpected side effects. All non-deterministic I/O, such as API calls or database queries, must be moved to dedicated step functions.

Question 3

How do I handle external API calls within a workflow?

Accepted Answer

You must delegate all external I/O operations to Step functions defined in separate files. The workflow function then calls these steps and orchestrates their results.

Question 4

Why are .js extensions required in my TypeScript imports?

Accepted Answer

The Output SDK follows strict ES Module (ESM) standards. In ESM, relative imports must include the file extension, which is .js for the transpiled output even when writing in TypeScript.

Output SDK Workflow Orchestrator

Key Features

Use Cases

REST API Design Patterns

Qa Javascript Typescript

Bun Runtime Optimizer