> 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/stackai-tools/workflow-and-catalog-tools/create-workflow.md).

# Create Workflow

Create a project by importing an existing workflow file. Use it to reuse a workflow definition without recreating its nodes manually.

## Import a workflow file

1. Provide **File URL** for the `.json` or `.stackai` workflow file.
2. Set **Workflow Name** and **Folder ID** if you want a specific name or location. Otherwise, the file name and current workflow’s folder are used.
3. For an encrypted `.stackai` file, supply its **Password**.
4. Run the action, check **Status**, and open **Workflow URL**. Review the imported configuration and required connections before running the new project.

**Result:** A successful import returns a link to the new workflow. If it fails, **Error** explains the problem.

## Behavior and troubleshooting

This action imports a file; it does not generate a workflow from a plain-language prompt. Importing a workflow does not prove that its external connections or resources are available in the destination organization.

## Inputs

| Field               | Parameter       | Description                                                                  |
| ------------------- | --------------- | ---------------------------------------------------------------------------- |
| File URL (required) | `file_url`      | URL of the .json or .stackai workflow file to import.                        |
| Folder ID           | `folder_id`     | Folder to create the workflow in. Defaults to the current workflow's folder. |
| Workflow Name       | `workflow_name` | Name for the new workflow. Defaults to the file name.                        |
| Password            | `password`      | Password to decrypt an encrypted .stackai file, if required.                 |

## Outputs

| Field        | Parameter      | Description                                                     |
| ------------ | -------------- | --------------------------------------------------------------- |
| Status       | `status`       | 'success' if the workflow was created, otherwise 'failure'.     |
| Workflow URL | `workflow_url` | Link to the created workflow (only present on success).         |
| Error        | `error`        | Error message describing why creation failed (only on failure). |

## Related guidance

[Action Inputs, Outputs, and Validation](https://docs.stackai.com/technical-reference/connections-and-tool-execution/action-inputs-outputs-and-validation.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/stackai-tools/workflow-and-catalog-tools/create-workflow.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.
