> For the complete documentation index, see [llms.txt](https://integrations.drivetrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-drivetrains-sftp.md).

# Integrating with Drivetrain's SFTP

Push files to the SFTP server Drivetrain hosts for you. Covers host, username and path, password or SSH key login, and file naming.

Use this page when **you push files to an SFTP server that Drivetrain hosts**. If Drivetrain should instead pull files from **your own** SFTP server, see [Integrating with SFTP](https://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-sftp.md).

### Get your SFTP details

Each workspace gets its own SFTP user and folder. You get the details in one of two ways:

* **In Drivetrain**, if your connector offers an SFTP option: choose **SFTP**, pick **Password** or **SSH Key** under **Select authentication method**, and click **View details**. For SSH Key, choose **Create for me** or **Enter my own key** (your public key).
* **From your Drivetrain team**, who share the same details with you.

**SFTP directory details** shows:

| Field               | Value                                                                                                        |
| ------------------- | ------------------------------------------------------------------------------------------------------------ |
| Host name           | `sftp.drivetrain.ai` for password login, `sftp1.drivetrain.ai` for SSH key login. Use the host shown to you. |
| Port                | `22`                                                                                                         |
| Username            | `dtuserXXX`, where XXX is your workspace's number                                                            |
| Destination path    | The folder for your connector, for example `/sftp-XXX/<connector name>`                                      |
| Password or SSH key | Shown **once**. Copy and store it securely: Drivetrain won't show it again.                                  |

To see the details again later (without the password or key), select **SFTP details** in the connection's menu on the **Data** page, if your workspace has it, or ask your Drivetrain team.

{% hint style="info" %}
A key that Drivetrain creates in the app has no passphrase. If your Drivetrain team gave you a passphrase, use it. Connect with, for example:

```
sftp -i <private_key_file> dtuserXXX@sftp1.drivetrain.ai
```

{% endhint %}

### Upload files

* Upload to the **Destination path**.
* Supported formats: CSV, Excel (XLSX, XLS), JSON, Parquet, and ZIP archives.
* File names: either overwrite one file each time (for example, `orders.csv`) or add a dated file each time (for example, `orders_YYYYMMDD.csv`).

When the files are added as data in Drivetrain (by you, if your workspace shows these options, or by your Drivetrain team), pick the option that matches your naming:

* **Bring selected files** — for a file you overwrite each time. New files with other names are ignored.
* **Bring latest files** — for dated files: Drivetrain loads the newest one.
* **Bring union of files** — for dated files you want combined into one table.

Each sync reloads the files in full.


---

# 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://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-drivetrains-sftp.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.
