> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/item-creation-sub-task.md).
# Item creation sub task
A sub workflow is an element in a User step
 \
**There are three types of sub workflows:**\
**Check List:** Executes one workflow for each record in a list of things to do.\
**Item Creation:** Creates a new item for each time the sub workflow is executed.\
**Verb:** A side track in the workflow where the sub workflow can be executed one or many times.
### Item Creation Sub Task
A sub workflow is created from a *User Step*. Create a new *User Step* and add a sub workflow element. Configure the appearance of sub workflow in the client.
**Set the following:**
* **Target Variable:** Enter a name for the output varibale. The output from the sub workflow will end up in this new table variable.
* **Title:** Text on the sub workflow button.
* **Icon:** Icon one the on the sub workflow button.
* **Sub Task Text:** Text on the Item (e.g. the Time Report) that has been created. Varibles can be added later.
* **New text:** Text on the New button, to add new item (e.g. a new Time Report)
* **Pills:** The indicator on the sub workflow button
* **Post-Blurbs:** Info parts on a created Item.
Close the *User Step*, an icon will now appear that representing the added sub workflow. Double click on the sub workflow icon to open the (empty) sub workflow. Create a workflow, all variables from the main workflow are available in the sub workflow. Return data back to the main workflow, by configuring the *End step* in the sub workflow.
---
# 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://help.novacuraflow.com/6.11/development/flow-studio/applications/workflow/user-step/item-creation-sub-task.md?ask=&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.
