# CODE PULL

```bash
bc CODE PULL
```

Pulls all Scripts and SQL Statements from your current account into your workspace `Code` directory, while maintaining the folder structure.

<div align="left"><figure><img src="/files/ym0g0rnRB4w0AGSeRkRG" alt="" width="264"><figcaption></figcaption></figure></div>

### Optional Parameters

<details>

<summary>/ComponentId, /c</summary>

Pull one or more specified component only.

</details>

<details>

<summary>/CodeDirectory, /wd /cd /d /out</summary>

Default: `Code`

Specify the folder where to put the code. The directory is relative to the current Workspace, or absolute.

</details>

<details>

<summary>/Folders, /f /base</summary>

Specify one or more Boomi folder names - semicolon separated list, from where to pull the code. The folder comparison is: full folder path starts with "specified folder". If you specify `/f Com` a ***Com**mon* folder is considered as well as a **Com**pany folder. Subfolders are always included.

The Full Folder Path is compared! If you have a folder, like: `script\98 - Sandbox` you should specify the path from the beginning `/f "script\98 - Sandbox"` - incl. quotes because of whitespaces.   &#x20;

</details>


---

# Agent Instructions: 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:

```
GET https://boomi.markusschmidt.pro/boomi-console/commands/code-sql-and-scripts/code-pull.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.