Start with documents in and structured output out. Then layer in review, user steps, risk scoring, or signing where the process actually needs them.
Not every flow needs the same path, but the core ingredients repeat. Korala gives you reusable workflow primitives for ingestion, extraction, validation, enrichment, review, and output.
This is the workflow story in motion: a document enters, OCR and extraction run, validations apply, and the output becomes usable for the rest of the business process.
The same underlying system can run proof-of-address, identity extraction, intake, review-heavy processes, or risk-oriented checks without creating a new product surface for each one.
Start with one document workflow, then combine it with sessions, review logic, and downstream actions without changing the integration model.
korala.workflows.run({ workflowSlug, inputData })workflowRun.output / workflowRun.validationssync, review, notify, or sign downstreamimport Korala from "@korala/sdk";
const korala = new Korala({ apiKey: process.env.KORALA_KEY });
const run = await korala.workflows.run({
workflowSlug: "proof-of-address",
inputData: {
country: "AE",
expectedDocumentType: "utility_bill",
},
});
console.log(run.status, run.output);Production workflows need more than a pass/fail badge. Teams need to understand what was extracted, which checks ran, and when a case should move into manual review.
Workflow-heavy usage generally lives under API Platform pricing, where documents, template fills, signing events, and orchestration scale together.
Most workflow customers land on API Platform pricing. Standalone Signing remains available when the job is primarily document execution and signature collection.
Start with ingestion and extraction, add validation and enrichment, then route the result into review, downstream systems, or signing.