> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/compare-the-stackai-project-and-beta-nodes.md).

# Compare the StackAI Project and Beta nodes

The StackAI Project and StackAI Project (Beta) nodes let you use an existing workflow as a step in another workflow. Use them when several workflows need the same process, such as a document review or a calculation.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FetyoI7AyLxJddyY1BdoL%2FG025A.mp4?alt=media&token=5437a55e-716b-4387-9937-79b098e9f9d7>" %}

## Choose the node for your task

| What your workflow needs                                            | Node to consider                      | Why it matters                                                            |
| ------------------------------------------------------------------- | ------------------------------------- | ------------------------------------------------------------------------- |
| Answer updates while the reused workflow is running                 | StackAI Project                       | The original node can return updates before the complete answer is ready. |
| List items processed one at a time with shared conversation context | StackAI Project with Loop Mode        | Earlier items can affect later items through that conversation.           |
| Independent list items and a completed result for each item         | StackAI Project (Beta) with Loop Mode | Each item has a separate conversation. Results remain in input order.     |

Both nodes reuse the selected workflow. The important choice is how its executions share conversation context and return results, not whether one node has a more recent name.

## Choose a workflow to reuse

Run the workflow you want to reuse and inspect its result.

![Reusable workflow and checked result](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/65W9LRSYXSIIzqEAIGI7/assets/g025a-01-reusable-check.png)

Confirm that its required inputs and returned values fit the work you need to perform.

## Use StackAI Project

Open the StackAI Project node's Settings and select the workflow in Choose StackAI Project.

![StackAI Project workflow selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/luyihTZpK2Zc3PCS9u8w/assets/g025a-02-original-project-setup.png)

This reuses its existing processing steps inside the current workflow.

Open Inputs and supply the required values.

![StackAI Project input values and Loop Mode](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/hBdGEZicptpoj60z9vjx/assets/g025a-03-list-inputs.png)

Set Loop Mode to Yes when you want one execution for each item in a list.

Run the original node and expand Output.

![Original project-node output for list items](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/PyXlzEiNTyTYdm4IUpiQ/assets/g025a-04-original-results.png)

It processes list items one at a time. Check that the returned answers correspond to the items supplied.

## Use StackAI Project (Beta)

Select the same workflow in StackAI Project (Beta) and configure its Inputs and Loop Mode.

![Beta workflow selection, inputs, and Loop Mode](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/sTvd1OsSusbVba1u5Vv9/assets/g025a-05-beta-setup.png)

Use Beta when list items can be processed independently and completed results meet your needs.

Run Beta and inspect the completed results.

![Completed Beta results in input order](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/llJC9XjEmRMZhD2eZw7M/assets/g025a-06-beta-results.png)

Results remain in input order even when individual items finish at different times.

## Inspect an individual execution

Open Analytics on the selected workflow and choose the relevant run.

![Called workflow execution in Analytics](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/vfX0E2egBwNIOme1ji93/assets/g025a-07-run-trace.png)

Run Details shows the input, output, and execution steps for investigating an individual result.

## Important behavior

The original node can return answer updates while the selected workflow runs. Beta returns completed results.

With Loop Mode enabled, the original node uses one conversation across the list. Beta uses a separate conversation for each item.

Beta retries eligible temporary failures. If the called workflow changes external records, account for the possibility that an operation runs again.

## Related steps

* [Loops and reusable project calls](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/loops-and-reusable-project-calls.md)
* [Workflow debugging and node results](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/workflow-debugging-and-node-results.md)


---

# 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.stackai.com/guides-and-quickstarts/workflow-builder/compare-the-stackai-project-and-beta-nodes.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.
