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

# CSV/SFTP

Further’s CSV/SFTP integration gives your team a **straightforward, low‑friction way to receive rich lead and visitor data** on a schedule that fits your reporting cadence. Instead of manually pulling reports, we automatically drop structured CSV files into a secure location (SFTP or email), so your data and analytics teams can plug them into existing dashboards, data lakes, or BI tools.

***

### How it Helps You

* **Automated, no‑click reporting**\
  Daily (or scheduled) CSV exports remove manual downloading and copy‑paste work—your team always has the latest files waiting where you expect them.
* **Easy to plug into your existing stack**\
  Because the integration delivers **standard CSV files to SFTP or email**, it works with almost any downstream system: data lakes, Domo, Looker, Excel, Google Sheets, or a homegrown warehouse.
* **Consistent structure for faster analytics**\
  We mirror the same core data model we use for Snowflake (e.g., **Prospects / Leads** and **Visitors**), so your analysts get clean, predictable columns for things like community, traffic source, contact details, and key journey fields.
* **Flexible fields and history**\
  We can tailor which columns you receive and how much history to backfill (for example, the last **18–24 months**), so you’re not overwhelmed with unused data.

***

### How it Works

1. **We align on what you want to see**\
   Together with your team (or agency), we confirm:
   * Which **data sets** you need (e.g., leads, visitors, tours, select CRM attributes).
   * Which **fields/columns** matter most for your reporting.
   * The **lookback window** (e.g., last 24 months) and **update frequency** (typically daily).
2. **We configure a secure delivery channel**\
   We set up one of the following:
   * **SFTP drop** – Further pushes CSV files to your SFTP server each day.
   * **Secure email or shared drive** – for lighter‑weight use cases or when SFTP isn’t available.
3. **We generate and deliver CSV files on a schedule**\
   A scheduled job in Further:
   * Builds the CSV export for the agreed‑upon time window (e.g., “all new and updated leads in the last 24 hours”).
   * Includes both **new records and updates**, based on your preferences (e.g., include updated leads in the same file).
   * Delivers the file to your SFTP folder or designated destination—ready for ingestion by your systems.
4. **Your team or partners ingest and join the data**\
   Your data team or agency:
   * Picks up the CSVs from SFTP (or email/drive).
   * Loads them into your **data lake, CRM, or BI tool**, and joins them with other sources like Yardi, WelcomeHome, ad platforms, and financial systems.

***

### In Closing

The CSV/SFTP integration is built for teams who want **automated, reliable data feeds without heavy engineering work**. It’s a great fit if you already have reporting infrastructure and just need fresh Further data to flow into it. If this sounds right for your organization, your CSM can help you scope the fields, cadence, and delivery method, then coordinate with our integrations team to get your feed live.


---

# 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.talkfurther.com/integrations/data-lake-integrations/csv-sftp.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.