> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/cli/project-manifest.md).

# Project Manifest

### Manifest

The `project` command is based on a `manifest.json` file. This definition document lets you define the contents of your WorkflowGen project and set your processes, sub-processes, custom applications, global lists, and custom assets (JavaScript, CSS, `.cs` files, etc.).

```json
{
  "version": "1.0",
  "tag": "1.1.0",
	"processes":[
    {
      "name":"PARENT_PROCESS2",
      "version":1,
      "folder":"DEFAULT"
    },
    {
      "name":"PARENT_PROCESS1",
      "version":1,
      "folder":"DEFAULT"
    }
  ],
  "subProcesses":[
    {
      "name":"SUBPROCESS",
      "version":1,
      "folder":"DEFAULT"
    }
  ],
  "globalLists": [
    "GLOBAL_LIST_DATA"
  ],
  "customApplications": [
    "MY_CUSTOM_APP"
  ],
  "webformAssets": [ 
    "js/myProcess/test.js",
    "js/global.js",
    "css/test.css",
    "appCode/Tools.cs",
    "img/logo.png"
  ]
}
```

| **Parameter**        | **Description**                                                                                                                 |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `version`            | Represents the manifest version; should always be `1.0`                                                                         |
| `tag`                | Represents your project version                                                                                                 |
| `processes`          | You can set zero or more processes in this array; for each item you should specify the `name` and the `version` of your process |
| `subProcesses`       | You can set zero or more processes in this array; for each item you should specify the `name` and the `version` of your process |
| `globalLists`        | You can set zero or more global lists in this array; you only need to specify the global list name                              |
| `customApplications` | You can set zero or more custom applications in this array; you only need to specify the custom application name                |
| `webformAssets`      | You can set zero or more assets in this array; for each asset, set the relative path to your asset based on your webform path   |

{% hint style="info" %}
During an import, the CLI will proceed in the following order:

* Custom applications
* Global lists
* Sub-processes
* Processes
* Webform assets

All items will be imported into the array in this order. Make sure that the link between processes is correct.
{% endhint %}

{% hint style="info" %}
You can use the [`project init`](/cli/list-of-commands.md#init) command to generate your manifest interactively.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/cli/project-manifest.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.