WorkflowGen CLI 2.0.0: Work with WorkflowGen from Your Terminal

WorkflowGen CLI 2.0.0 is now available!

The CLI brings WorkflowGen to your terminal with the wfg command. Whether you want to check requests, export process definitions, manage environments, or automate repetitive tasks, it provides a convenient way to work without needing to navigate through the web interface each time.

It runs on Windows, macOS, and Linux and connects through WorkflowGen’s MCP endpoint using your existing WorkflowGen identity and permissions.

What you can do with it

Work with requests and actions

You can find requests, inspect their details, view pending actions, launch processes, and perform authorized actions directly from the terminal.

For example, to list recent requests, inspect a specific request, and view the actions associated with that request:

wfg requests list --limit 10
wfg requests show 12345
wfg actions list --request 12345

Manage and transfer process definitions

Process administrators can create and manage processes, organize folders, and import or export complete definitions.

XPDL is supported across compatible WorkflowGen versions. WorkflowGen 9.7.0 and 10.4.0 also support JPDL, the JSON process-definition format. See the JPDL format reference article for information on the JPDL format.

For example, to export a process as JPDL:

wfg processes export --name EXPENSES --version 3 --format jpdl --output ./EXPENSES_3.json

You can also work with applications, global lists, participants, users, and other administrative resources, according to your permissions.

Switch between environments

The CLI also lets you save named connections for development, testing, and production, then select the environment you want to work with:

wfg auth profiles
wfg auth use test

This makes it easier to work across multiple installations. Always confirm the active environment before running commands that change data or import definitions.

Use WorkflowGen in scripts

Supported commands provide JSON output for use in scripts and other tools. For example:

wfg requests list --limit 10 --json
wfg whoami --json

You can use this to build repeatable checks, extract information, or incorporate WorkflowGen operations into your own automation.

Getting started

On the computer running the CLI, install Node.js with npm. The CLI requires Node.js 24.11.0 or later; use a current patched Node.js 24 LTS release.

Install the package:

npm install --global @workflowgen/cli
wfg --version

Ask your WorkflowGen Administrator for the MCP address, then create a named connection:

wfg auth login https://workflowgen.example.com/wfgen/mcp --name test

Replace the example URL with your environment’s address.

Your browser opens so you can sign in to WorkflowGen and authorize the connection. You do not enter your WorkflowGen password in the terminal.

After signing in, check your connection:

wfg auth status
wfg whoami
wfg doctor

You’re ready to explore:

wfg --help
wfg requests --help
wfg tools

Supported WorkflowGen versions

CLI 2.0.0 supports:

WorkflowGen version Database
9.x from 9.6.1, including 9.7.0 SQL Server
10.x from 10.3.1, including 10.4.0 SQL Server 2025 or PostgreSQL

Your Administrator must enable and configure MCP access. Available commands depend on the environment’s capabilities and your WorkflowGen permissions.

WorkflowGen 9.7.0 and 10.4.0 include MCP Server 1.0.0 and add JPDL import and export. For an introduction to MCP, see Getting Started with WorkflowGen MCP Server 1.0.0.

Your permissions still apply

The CLI does not bypass WorkflowGen security. Signing in grants access through your existing account; it does not give you additional roles or administrative rights.

Review commands carefully before changing data, completing actions, or importing processes. Saved authorization credentials are stored locally, so protect your workstation account and do not share the CLI configuration or tokens.

Already using an earlier CLI?

If you’re using the v2 beta, run the installation command again to update. Existing CLI v2 profiles are retained.

If you are moving from the former WorkflowGen.Cli .NET tool, CLI v2 is a separate npm package and requires a new sign-in. Both tools use the command name wfg, so check which executable your terminal uses if you keep both installed.

Learn more

The WorkflowGen CLI page on npm includes installation instructions, command examples, compatibility information, and troubleshooting.

Try it with a test environment, start with wfg whoami, and explore how the CLI can simplify your everyday WorkflowGen tasks!