> 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-sftp.md).

# Integrating with SFTP

Let Drivetrain pull files from your own SFTP server. Covers the details to share, password login, and supported file formats.

Use this page when **Drivetrain pulls files from an SFTP server you host**. If you'd rather push files to an SFTP server Drivetrain hosts, see [Integrating with Drivetrain's SFTP](https://integrations.drivetrain.ai/integration-guide/readme/others/integrating-with-drivetrains-sftp.md).

Your Drivetrain team sets up this connection. Share the details below with them through a secure channel.

## Required details <a href="#required-details" id="required-details"></a>

1. **SFTP host and port**: the hostname or IP address of your SFTP server and the port (usually `22`). For example: `sftp.yourcompany.com:22`
2. **SFTP username** and **password**. Drivetrain signs in with a username and password; SSH key login isn't supported for this connection.
3. **SFTP folder path**: where the files are placed. For example: `/exports/`, `/data/outgoing/`
4. **File names**: which files to fetch. If names include dates or timestamps, give the naming format. For example: `orders_YYYYMMDD.csv`, `export.csv`

## File requirements

* **CSV** or **Excel** (XLSX, XLS) files. In Excel files, each sheet becomes its own table.
* Each sync reloads the files in full.

## Best practices <a href="#best-practices" id="best-practices"></a>

1. Create a **dedicated SFTP user** with read access to only the relevant folder.
2. If your firewall restricts access, ask your Drivetrain team for the IP address to allowlist.


---

# 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-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.
