> 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/onboarding/customers-connect-and-customize.md).

# Step 4: Customers connect and customize

Onboarding step 4. Customers connect their own accounts in the widget and adjust each integration; you try it once as a test customer.

This step is for what your customers do: connect their own accounts in the widget and adjust each integration to how they work. Integrations then run for each customer with that customer's own connections and settings.

**Why:** every customer's data is different. When customers customize integrations themselves, you don't build a version per customer. Doing it once yourself, as a test customer inside your product, proves the whole chain works: your product, the widget, the connection and the workflow.

### Without fastn and with fastn

|                      | Without fastn                                                                           | With fastn                                                                                           |
| -------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Connecting           | Customers send credentials to your support team, or you build a connect flow per system | Customers sign in to each system in the widget; their credentials stay theirs                        |
| Customizing          | Feature requests and custom code per customer                                           | Customers change mappings, filters and direction in **Configure**, or with the widget's AI assistant |
| Knowing it works     | Customers report what broke                                                             | **Insights** shows runs and connection health, with alerts by email, Slack, Teams or webhook         |
| Supporting customers | Search your own logs                                                                    | You see each customer's connections, runs and events, and can replay a failed delivery               |

### What it's made of

| Component           | What it is                                                                                                   |
| ------------------- | ------------------------------------------------------------------------------------------------------------ |
| Customer            | One of your customers. It must be Active before its integrations run                                         |
| Connection          | A customer's signed-in account on one system                                                                 |
| Configuration       | A customer's own direction, field mappings and filters, copied from the integration's configuration template |
| AI assistant        | The customer describes a change in plain words and reviews it before saving                                  |
| Insights and alerts | Runs, records, errors and connection health, with failure and threshold alerts                               |

### Ways to do it

| Way              | How the customer connects                                                                                                                          |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| In the widget    | **Connect**, sign in on the system's own page, then **Authorize**                                                                                  |
| Shareable link   | Opens a link you send                                                                                                                              |
| Created for them | Your backend creates the connection with credentials you already hold ([step 3](https://docs.fastn.ai/get-started/onboarding/embed-the-widget.md)) |
| A second account | **Add another connection**, where the integration allows it                                                                                        |

### Use cases and scenarios

| Use case                | What the customer does                                           |
| ----------------------- | ---------------------------------------------------------------- |
| Different field names   | Maps their "Region" field to your "Territory"                    |
| Only some records       | Adds a filter, for example only deals above a value              |
| One way instead of two  | Turns off one direction of a two-way sync                        |
| A change in plain words | Asks the widget's AI assistant, then reviews each labeled change |
| Something broke         | Sees it in **Insights**, or reconnects an expired connection     |

### What to know

* **Activate customers.** A customer in **Pending admin activation** can't run integrations until an admin activates it.
* **First-time setup.** A configurable integration needs its first configuration made once by your team (Operator role or higher). Until then, the customer's **Configure** shows "No configuration found for this widget".
* **Changes apply on the next run.** Records already synced keep their old values.
* **The AI assistant** opens from the sparkle button at the bottom right of the widget (**Ask the assistant**). It can add or remove fields, narrow which records sync, fix field pairings and change direction. It can't add a system you don't offer, re-sync old records, change the schedule or add custom logic.
* **Limits.** Customers share your plan's limits. Change one customer's in **Settings** → **Billing** → **Customize customer limits**.

### In the onboarding

You open your product where the widget is embedded, as a test customer, then connect and customize the integration from [step 2](https://docs.fastn.ai/get-started/onboarding/choose-integrations.md). Onboarding lists each real event from your product (widget loaded, connected, customized, first run) and unlocks **Finish** on a live connection. Finishing the step earns 10 AI credits.

### Related docs

[Customers](https://docs.fastn.ai/operate/customers.md) · [Managing customers](https://docs.fastn.ai/operate/customers/managing-customers.md) · [Connection statuses](https://docs.fastn.ai/operate/connections/statuses.md) · [Customizing your integrations](https://docs.fastn.ai/for-your-customers/end-user/customizing-your-integrations.md) · [Extending a pre-built integration](https://docs.fastn.ai/for-your-customers/end-user/extending-a-prebuilt-integration.md) · [Getting alerted](https://docs.fastn.ai/for-your-customers/end-user/getting-alerted.md) · [Troubleshooting](https://docs.fastn.ai/operate/troubleshooting.md)


---

# 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/onboarding/customers-connect-and-customize.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.
