> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/workflow-start.md).

# Workflow Start

### Description

This part starts an instance of a workflow. It will therefore create a record of the workflow in the generic\_workflow table and return the instance ID of the workflow.

Optionally the: user-id and the instance ID of a parent workflow can be provided to store with the workflow information in the table.

### Use

Add the part to a process-node and configure its parameters. Once the process-node is executed a new instance of a workflow has been created.

### Editor Fields

| Group | Field                | Type / Options | <p>Optional/<br>Mandatory</p> | Description                                                      |
| ----- | -------------------- | -------------- | ----------------------------- | ---------------------------------------------------------------- |
| Basic | User-id              | Text           | O                             | The id of the user that requested the start of the workflow      |
| Basic | Parent Workflow-id   | Integer        | O                             | The instance ID of the parent workflow                           |
| Basic | Workflow-id saved to | Data object    | O                             | The data object to store the instance ID of the started workflow |

**Example**

None


---

# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/workflow-start.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.