Workflow SDK makes TypeScript and JavaScript functions durable. It persists workflow progress, retries failed steps, and provides built-in observability. Workflows can suspend without using compute while they wait.
Install the SDK in an existing project:
npm install workflowConfigure the integration for your framework. For example, with Next.js:
// next.config.tsimport{withWorkflow}from'workflow/next';exportdefaultwithWorkflow({});Then start a workflow from an API route, Server Action, or other server-side code:
import{start}from'workflow/api';import{onboardUser}from'./workflows/onboard-user';awaitstart(onboardUser,['hello@example.com']);Run your app, then open the local observability UI in another terminal:
npm run devnpx workflow webChoose your framework in the getting-started guides.
Note
The workflow package includes its full documentation, so coding agents can
read version-matched guides locally from node_modules/workflow/docs.
Local development uses the bundled backend with no configuration. Deploy to Vercel for managed storage, queuing, scaling, and observability. To self-host, use the Postgres backend or implement a custom World.
There are many third-party Worlds (both self-hosted or managed), see the Worlds page for a list of maintainer-curated third party worlds. Submit your world by opening updating the Worlds Manifest.
The Workflow SDK community lives on GitHub Discussions, where you can ask questions, share ideas, and show what you have built.
Contributions are welcome. Use issues and discussions to collaborate with the team and wider community. By participating, you agree to our Code of Conduct.
If you believe you have found a security vulnerability in Workflow SDK, we encourage you to responsibly disclose this and not open a public issue.
To participate in our Open Source Software Bug Bounty program, please email responsible.disclosure@vercel.com. We will add you to the program and provide further instructions for submitting your report.