> For the complete documentation index, see [llms.txt](https://docs.pollination.solutions/user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pollination.solutions/user-manual/grasshopper-plugin/grasshopper-user-interface/2_pollination/upload_assets.md).

# Upload\_Assets

![Upload Assets](/files/I3oIkDWiVNG5lMFOsgqG)

Upload local files and folders to Pollination cloud server, and they will be used as cloud asset references.

## Inputs

* **project \[Required]**

  Project that all artifacts will be uploaded to. Use GetProject component or a name for getting a project from the current user. To get a project under another account, you can specify the account name before the project name with the format: AccountName/ProjectName. For example: pollination/NewDemoProject
* **artifacts \[Required]**

  File or folder paths to be uploaded to the Pollination cloud.
* **sub\_folder \[Optional]**

  An optional input for relative folder path where you want to save all Pollination job's files, instead of project root folder. For example: "Phase 1/Team A"
* **upload \[Required]**

  Set to true to upload the assets.

## Outputs

* **status**

  status.
* **artifacts**

  artifacts that have been uploaded to the Pollination cloud.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pollination.solutions/user-manual/grasshopper-plugin/grasshopper-user-interface/2_pollination/upload_assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.