> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/get-started/readme.md).

# Welcome to fastn

fastn is the embedded integration platform for SaaS. Embed one widget and your customers connect, customize and build their own integrations inside your product, while fastn keeps them working.

**fast(e)n your product to everything.**

fastn is the embedded integration platform for SaaS. You embed the fastn widget in your product once. Your customers then connect their own accounts, turn on the integrations they need, and shape them around how they work. fastn handles authentication, data mapping, retries, rate limits and monitoring, and keeps every integration working as the apps underneath change.

The result: you close the deals you were losing to a missing integration, keep the customers you were churning, and keep your engineers on your product.

## The problem fastn solves

Every customer asks for integrations. Some you already have, but they need to fit how each customer works. Some you don't offer at all. Your team can't build and maintain them all, and handing customers your API docs just moves the work onto them. Either way, you risk losing the customer.

## How it works

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-3bd975880270f7fafbd98a47e45a9644ce9dda78%2Ffastn-lifecycle.svg?alt=media" alt="The fastn integration lifecycle: who does what across Build, Publish, Embed, Customize, and Run and monitor"><figcaption><p>Five stages, three parties: your team, your customer and fastn</p></figcaption></figure>

{% stepper %}
{% step %}

### Build

Your integration builder describes the integration in plain words, with **Build with AI** in the dashboard, or from your AI tool, such as Claude or Cursor, over MCP. fastn's agent picks the connectors, writes the workflow, and generates and runs test cases. [Build with the agent](/build/build.md)
{% endstep %}

{% step %}

### Publish

You save, publish and deploy a version, then add it to your widget's integration catalog and choose what each customer is allowed to change. [Build your widget](/embed/widget-builder/building-your-widget.md)
{% endstep %}

{% step %}

### Embed

Your developer drops the widget into your product with an iframe or the SDK. Your backend issues a short-lived token per customer, so every connection is scoped to the right customer. [Embed the widget](/embed/embedding.md)
{% endstep %}

{% step %}

### Customize

Inside your product, each customer connects their own accounts, maps fields to fit how they work, and can ask the widget's AI assistant for a change or an integration that doesn't exist yet. Nothing ships until it is approved. [What your customers see](/for-your-customers/end-user.md)
{% endstep %}

{% step %}

### Run and monitor

**Health** shows what needs attention across every customer, with the fix for each, and alerts tell you when a run fails. fastn handles retries, rate limits and token renewal, and its agents catch API changes and propose the fix. [Operate](/operate/overview.md)
{% endstep %}
{% endstepper %}

## Start here

Pick the path that matches what you're doing today.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>New to fastn</strong></td><td>The five building blocks and how a build fits together, in ten minutes.</td><td><a href="/get-started/getting-started.md">How fastn works</a></td></tr><tr><td><strong>Build your first integration</strong></td><td>Describe an integration to the agent and get a tested, working workflow.</td><td><a href="/get-started/quickstart.md">Quickstart: your first integration</a></td></tr><tr><td><strong>Embed it in your product</strong></td><td>For developers: render the widget and generate tokens from your backend.</td><td><a href="/embed/embedding/embedding-quickstart.md">Embedding quickstart</a></td></tr><tr><td><strong>Test, deploy and release</strong></td><td>Test cases, versions, environments, and shipping a change safely.</td><td><a href="/build/lifecycle.md">Test and release</a></td></tr><tr><td><strong>Monitor and get alerted</strong></td><td>Health, alerts and every customer's runs, in one place.</td><td><a href="/operate/health.md">Health</a></td></tr><tr><td><strong>Help for your customers</strong></td><td>Pages you can share with the people using integrations inside your product.</td><td><a href="/for-your-customers/end-user.md">Using integrations in the widget</a></td></tr></tbody></table>

## Two audiences, one platform

| Who                                   | Where they work                                                                              |
| ------------------------------------- | -------------------------------------------------------------------------------------------- |
| **You**, the SaaS company using fastn | The fastn dashboard: build integrations, embed the widget, monitor and manage                |
| **Your customer**                     | The fastn widget inside your product. They never need a fastn account or to sign in to fastn |

## Words we use

* An **integration** is a connector, a connection, its triggers (app event, schedule or webhook) and the workflow logic around them.
* The **integration catalog** is the set of integrations your customers can turn on in the widget.
* **SaaS company** means you, fastn's customer. **Customer** means your own customer.

The full list is in the [Glossary](/reference/glossary.md).

## Need help?

Check the [FAQs](/reference/faqs.md) and [Troubleshooting](/operate/troubleshooting.md), or [book a demo](https://fastn.ai) to see fastn running inside a product like yours.


---

# 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.fastn.ai/get-started/readme.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.