> 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-mcp/tool-reference/projects-and-workflow-authoring/projects-import.md).

# projects\_import

Create a new draft from a parsed exported workflow\_json object, optionally overriding project\_name and folder\_id.

**Effect:** This call saves data or changes configuration. Review the behavior below before using it.

## Inputs

| Name            | Type   | Requirement | Description                                                                                            |
| --------------- | ------ | ----------- | ------------------------------------------------------------------------------------------------------ |
| `workflow_json` | object | Required    | Complete parsed StackAI workflow export, as an object. Do not pass a JSON string or a signed file URL. |
| `project_name`  | string | Optional    | Optional name for the imported project; otherwise use the exported name.                               |
| `folder_id`     | string | Optional    | Optional destination folder ID. If omitted, the default destination is used.                           |

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

Build the arguments from your complete exported file; this preserves fields that a hand-written minimal export could omit.

```python
import json
from pathlib import Path

arguments = {
    "workflow_json": json.loads(Path("workflow.json").read_text()),
    "project_name": "Imported workflow",
}
```

Pass `arguments` to `projects_import` in your MCP client.

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "project_id": "<new-project-id>",
  "name": "<project-name>",
  "project_url": "<project-url>"
}
```

## Behavior

This does not edit an existing project and is not idempotent.

Keep the serialized export below roughly 200 KiB and within the transport envelope.

Validate the draft and resolve connections for the target organization before publishing.

## Troubleshooting

For an oversized export, use project import in the StackAI interface. File upload tools store bytes and do not import a workflow. After an uncertain response, inspect projects before importing again.

## Related resources

[Projects and workflow authoring](https://docs.stackai.com/stackai-mcp/tool-reference/projects-and-workflow-authoring.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.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-mcp/tool-reference/projects-and-workflow-authoring/projects-import.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.
