> ## Documentation Index
> Fetch the complete documentation index at: https://cobalt-55-abhishek.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Add native third-party integrations to your product so your customers connect their own apps and your features act on their data.

Native is Refold's product for embedding third-party integrations inside your own SaaS product. Use it to let your customers connect the apps they already use (Salesforce, HubSpot, NetSuite, and [300+ more connectors](/v3/platform/concepts/connector/supported-apps-actions)) and to read, write, and sync their data from your features, without building or maintaining a separate integration for each app.

You ship the connect experience and the in-product settings. Refold handles authentication, token refresh, execution, and tenant isolation. No per-app OAuth code. No credential storage. No integration backend to operate.

## Who Native is for

Native is for product and engineering teams who want integrations to be a feature customers turn on themselves, not a service you deliver one customer at a time.

* **Your customers** connect their own third-party accounts from inside your product and choose what each integration does for them.
* **Your engineers** embed a connect flow, collect per-customer settings, and call Refold to move data, using the [SDKs](/v3/api-reference/javascript-sdk) and [API](/v3/api-reference/overview).

<Info>
  If you instead scope and deliver bespoke enterprise integrations one project at a time, use Integration Delivery. Native is for self-serve, in-product integrations.
</Info>

## The embed model

A Native integration has three moving parts that you wire together once and reuse for every customer:

* **A [linked account](/v3/platform/concepts/linked-account)** represents one of your customers. You create one per customer and scope every connection and data call to it.
* **A [connector](/v3/platform/concepts/connector/supported-apps-actions)** is a supported third-party app. You enable the connectors your customers can connect to.
* **A [workflow](/v3/platform/concepts/workflows/overview)** is the automation that moves data between your app and a connected app. You build it once on the platform and expose it to customers.

Customers connect an app through a [frontend flow](/v3/native/frontend/overview) you embed, fill in [config fields](/v3/native/configure/integration/config-fields) so the integration fits their account, and your product then reads and writes their data through Refold. For the full picture of what runs where, see [How Native works](/v3/native/get-started/how-it-works).

## The builder journey

Building a Native integration follows the same path every time:

<Steps>
  <Step title="Run the Quickstart">
    Connect a real account and write data to it end to end in about 15 minutes. See the [Quickstart](/v3/native/get-started/quickstart).
  </Step>

  <Step title="Embed the connect experience">
    Let customers authorize their apps from inside your product. Choose a [frontend flow](/v3/native/frontend/overview): the hosted portal, the React SDK, or a build-your-own UI.
  </Step>

  <Step title="Collect per-customer settings">
    Add [config fields](/v3/native/configure/integration/config-fields) so one connector adapts to each customer's account without bespoke code.
  </Step>

  <Step title="Move data">
    Read, write, and [sync data](/v3/native/move-data/read-write) between your product and your customers' connected apps.
  </Step>

  <Step title="Ship and operate">
    Walk the [go-live checklist](/v3/native/ship-and-operate/go-live) and [monitor](/v3/native/ship-and-operate/monitoring) connection health in production.
  </Step>
</Steps>

## Explore the docs

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/v3/native/get-started/quickstart">
    Take your first integration live end to end.
  </Card>

  <Card title="How Native works" icon="diagram-project" href="/v3/native/get-started/how-it-works">
    The architecture and mental model behind the embed.
  </Card>

  <Card title="Frontend" icon="window" href="/v3/native/frontend/overview">
    Embed the connect experience in your product.
  </Card>

  <Card title="Configure" icon="sliders" href="/v3/native/configure/integration/config-fields">
    Collect per-customer settings with config fields.
  </Card>

  <Card title="Move data" icon="arrows-rotate" href="/v3/native/move-data/read-write">
    Read, write, and sync data through Refold.
  </Card>

  <Card title="Recipes" icon="book-open" href="/v3/native/recipes/netsuite">
    Follow end-to-end builds for real connectors.
  </Card>
</CardGroup>