> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/file-automation-sftp/user-data-uploads-via-sftp.md).

# User Data Uploads via sFTP

You can automate user data uploads by sending CSV file templates to Unimarket via **Secure File Transfer Protocol (sFTP)**. This service removes the need to manually manage user profiles by securely importing data directly into your community.

## Prerequisites

* **Enable Feature**: The upload feature must be enabled by Unimarket; contact your **Customer Success Manager** to discuss and enable this option.
* **sFTP Setup**: Before sending files, the sFTP functionality must be configured, including IP whitelisting and authentication. See [sFTP Setup for File Automation](/documentation/file-automation-sftp/sftp-setup-for-file-automation.md).

## sFTP Setup Process

Follow these steps to establish a secure connection for your user data uploads:

1. **Enable Functionality**: Unimarket enables sFTP, providing a secure location for your CSV files.
2. **Connection Details**: Unimarket will provide the specific **command line** needed to connect to the sFTP server.
3. **Authentication**: Establish access via an integration user password or a **public key** provided by the customer (preferred option).
4. **IP Whitelisting**: Provide your **IP address** to Unimarket for whitelisting.

{% hint style="info" %}
**Note:** You will experience a connection timeout if your IP is not whitelisted.
{% endhint %}

5. **Connect**: Once setup is confirmed, use an sFTP client to connect to the server.

### Loading Files

To ensure data is handled accurately, follow these processing rules:

* **Sequential Uploads**: Files must be **sent in order**. Each file must be fully uploaded before the next one is sent; do not send them all at once.
* **Inbound Location**: Send files to the designated **inbound folder** on the sFTP server.
* **Post-Processing**: Once processed, files are automatically moved to the **processed folder** and its relevant sub-directories.

## File Naming Convention

* **Standard**: User files do not require a specific naming convention.
* **Action**: Simply deliver the file to the corresponding folder on the sFTP server, for it to be picked up for processing.

## Troubleshooting: Problem Processing File Error

If you receive a **"Problem Processing File"** notification:

1. Navigate to the **Administration** module and select **File Processing**.
2. Hover over the **"i" icon** to view the specific error details.
3. Correct the CSV data and re-upload the file.

See [sFTP File Error: Problem Processing File](/documentation/file-automation-sftp/sftp-file-error-problem-processing-file.md) for more detail.


---

# 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.unimarket.com/documentation/file-automation-sftp/user-data-uploads-via-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.