openworkflow.dev valid

OpenWorkflow

Open-source durable workflow engine for TypeScript, powered by PostgreSQL or SQLite.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:58:12.238Z. Cached copy · Source on openworkflow.dev

# OpenWorkflow

> Open-source durable workflow engine for TypeScript, powered by PostgreSQL or SQLite.

> ## Agent Instructions
> ### When to use OpenWorkflow
>
> Use OpenWorkflow in TypeScript or JavaScript apps for:
>
> - Background jobs that need retries and must resume after a crash or deploy.
> - Multi-step integrations and data pipelines that need to save progress between operations.
> - AI workflows with multiple model or tool calls that need durable checkpoints.
> - Workflows that wait for a human approval, a webhook, or a timer before continuing.
>
> OpenWorkflow runs on Node.js 22.22+ or Bun, with PostgreSQL or SQLite storing workflow state. Your app enqueues runs, and a worker executes them.
>
> ### How to use OpenWorkflow
>
> Read and follow https://openworkflow.dev/skills/setup.md to set up OpenWorkflow.
>
> Define workflows with `defineWorkflow`, wrap operations in `step.run`, and enqueue runs with `ow.runWorkflow(workflow.spec, input)`. Start a worker with `npx @openworkflow/cli worker start` to execute them. See [Workflows](https://openworkflow.dev/docs/workflows.md), [Steps](https://openworkflow.dev/docs/steps.md), and [Signals](https://openworkflow.dev/docs/signals.md) for the APIs.

- [OpenWorkflow](https://openworkflow.dev/index.md): OpenWorkflow is an open-source durable workflow engine for TypeScript, powered by PostgreSQL or SQLite.
- [Quick Start](https://openworkflow.dev/docs/quickstart.md): Get up and running with OpenWorkflow in 5 minutes, from installing the CLI to running and inspecting a workflow
- [Overview](https://openworkflow.dev/docs/overview.md): How OpenWorkflow works and how Workflows, Steps, and Workers fit together to save progress and recover after a crash
- [Workflows](https://openworkflow.dev/docs/workflows.md): Durable functions that survive crashes and resume where they left off, with completed steps saved in your database
- [Steps](https://openworkflow.dev/docs/steps.md): Durable checkpoints that don't repeat already completed work, saving step results for retries and crash recovery
- [Workers](https://openworkflow.dev/docs/workers.md): Long-running processes that execute your workflows, poll for runs, and resume unfinished work after worker crashes
- [Sleeping](https://openworkflow.dev/docs/sleeping.md): Pause workflows for seconds, hours, or months without blocking resources, with timers that survive worker restarts
- [Recurring schedules](https://openworkflow.dev/docs/schedules.md): Run workflows on a recurring schedule using cron expressions and your existing workers
- [Parallel Steps](https://openworkflow.dev/docs/parallel-steps.md): Run multiple steps concurrently for better performance with Promise.all and saved results for each completed step
- [Dynamic Steps](https://openworkflow.dev/docs/dynamic-steps.md): Run a variable number of steps based on runtime data, with saved results per item and stable IDs for changing lists
- [Child Workflows](https://openworkflow.dev/docs/child-workflows.md): R
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=openworkflow.dev · GET /v1/domain/openworkflow.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for openworkflow.dev:
1. POST https://agentwebmap.com/v1/sites/openworkflow.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://openworkflow.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/openworkflow.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openworkflow.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.