> ## Documentation Index
> Fetch the complete documentation index at: https://docs.filefeed.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Concepts

> Understand FileFeed fundamentals: Connections, Schemas, Pipelines, Pipeline Runs, and Webhooks

<Note>
  The entity formerly called **Client** was renamed to **Connection** in API
  version `2026-05-25`. Old names (`/clients`, `filefeed.clients`, `Client`
  type) still work for 12 months — see the [migration guide](/migration/v1-to-v2).
</Note>

## Overview

FileFeed streamlines file-based integrations through two primary paths:

* **Embedded Importers**: In-app data import experiences (React SDK)
* **Automated Flows**: Backend-driven automation via SFTP (inbound) or API (outbound), with webhooks and SDK

## Compare at a glance

| Aspect       | Embedded Importers                    | Automated Flows                                  |
| ------------ | ------------------------------------- | ------------------------------------------------ |
| Trigger      | User-initiated in-app                 | SFTP upload, API push, or scheduled              |
| Typical user | Product/Operations teams              | Backend/Integrations teams                       |
| Data entry   | UI mapping, preview, validate         | File drop to SFTP or JSON push via API           |
| Validation   | In-app field + custom rules           | Schema validation during processing              |
| Processing   | Client app                            | FileFeed pipelines + your backend via webhooks   |
| Output       | Records to your app                   | Webhook event + fetch processed data via API/SDK |
| Best for     | Self-serve onboarding, ad-hoc imports | Continuous or automated partner feeds            |

## Embedded Importers

### What it is

* In-app import experience powered by the React SDK
* Validates and transforms data client-side before sending

### When to use

* Product-led import UX inside your app
* One-off or occasional imports initiated by users

### How it works

1. Render the importer in your app
2. Map/validate fields and preview results
3. Submit to your backend to persist/process

<CardGroup cols={3}>
  <Card title="Overview" icon="book-open" href="/embedded-importers/overview">
    High-level concepts and flow.
  </Card>

  <Card title="React SDK" icon="react" href="/embedded-importers/react-sdk">
    Embed the importer in your app.
  </Card>

  <Card title="Configuration" icon="gear" href="/embedded-importers/configuration">
    Workbooks, fields, transforms, validations.
  </Card>
</CardGroup>

## Automated Flows

### Building Blocks

<CardGroup cols={3}>
  <Card title="Connections" icon="plug" href="/automated-flows/sftp-flow#2-connections">
    Dedicated SFTP space and credentials per data source. Previously called "Clients".
  </Card>

  <Card title="Schemas" icon="database" href="/automated-flows/sftp-flow#3-schemas">
    Define fields and validation to ensure consistent data.
  </Card>

  <Card title="Pipelines" icon="shuffle" href="/automated-flows/sftp-flow#4-pipelines">
    Connect a Connection + Schema, add mappings and transforms. Supports inbound (SFTP) and outbound (API) directions.
  </Card>

  <Card title="Outbound Uploads" icon="arrow-up-from-bracket" href="/automated-flows/outbound">
    Push JSON data into pipelines via API instead of SFTP.
  </Card>

  <Card title="Pipeline Runs" icon="activity" href="/automated-flows/sftp-flow#1-retrieving-files-by-pipeline-run-id">
    Per-file processing with status and data retrieval.
  </Card>

  <Card title="Webhooks" icon="bell" href="/automated-flows/sftp-flow#1-understanding-webhooks">
    Event notifications with signed payloads.
  </Card>
</CardGroup>

<Note>
  Use webhooks to trigger data syncs. Use the REST API/SDK to fetch full processed data.
</Note>

## Choosing an Integration Path

<Columns cols={2}>
  <Card title="Embedded Importers" icon="react" href="/embedded-importers/overview">
    Best for product teams who want a beautiful, guided import UX inside their app.
  </Card>

  <Card title="Automated Flows" icon="server" href="/automated-flows/overview">
    Best for backend integrations, SFTP workflows, or scheduled data ingestion.
  </Card>
</Columns>