> 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/build/saas-connectors.md).

# Connect your product

Connecting your own product, through its API or webhooks, and the scopes your customers connect under.

**Build → Connect your product → API connector**

> Connect your product through its API or webhooks, so each customer's connection to it can be scoped, and tell fastn where to call your product back. Integrations can't go live until your product is connected.

Every other connector in fastn represents someone else's system: Shopify, HubSpot, Jira. This page is for the opposite case: **your own product**, through its API or webhooks, registered so that each of your customers has a connection to your product, scoped the way your product is organized.

An integration usually has two ends. One end is the app your customer uses, picked from **Integrations**. The other end is your product, connected here. Workflows read and write both through the same kind of connection. You can explore and build before this is done, but no integration goes live until your product is connected.

The sidebar row shows for Owners and Admins. The page itself opens for Owners, Admins, Developers and Operators, but only Owners and Admins can save a connector or its scopes. The **Webhooks** tab shows for Owners, Admins and Developers; Operators see the connector tab only.

With nothing registered the page reads:

> Your product is not connected yet. Pick the connector for your product, through its API or webhooks, and define connection scopes (e.g. inventory, product) that your customers' connections to it are created under.

### Connecting it

**Connect your product** opens the **Connect your product** panel, which takes two things.

| Field                 | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Connector \***      | A picker over every connector you can see, except ones already registered here (*Select your product's connector…*). Its helper text is the important part: *"The connector for your own product, through its API or webhooks: the one your customers' connections are made against."* This is not the system you are integrating **with**; it is the one representing **you**. If your product is not in the catalog yet, create its connector first from **Integrations → Connectors → Create connector**. |
| **Connection scopes** | A free-text field with an **Add** button beside it (press Enter or click **Add**). The list starts empty; `inventory` is only the placeholder text. Scopes are lowercased and can be at most 50 characters. Add as many as you need.                                                                                                                                                                                                                                                                         |

The panel closes with **Cancel** and **Add connector**.

### What a scope is for

The helper text under the scopes field states the rule directly:

> Each customer holds at most one connection per scope (e.g. inventory, product). A widget tags your product's connector with a scope, and installation pins the customer's matching connection.

Three consequences worth being deliberate about:

* **One connection per customer per scope.** A scope is the uniqueness key. A customer cannot hold two `inventory` connections to your product, so a scope is how you stop a customer from accidentally wiring the same thing twice.
* **Widgets tag against a scope.** The [widget](https://docs.fastn.ai/embed/widget-builder.md) names the scope it wants, which is what lets one widget resolve to the right connection for whichever customer is looking at it.
* **Turning on an integration pins the match.** When a customer turns on an integration, the connection matching that scope is the one bound, so the scopes you choose here decide how granular each customer's setup can be.

Pick scopes that name a *capability boundary* in your own product (`inventory`, `product`, `billing`), rather than one scope per customer. Customers are already one axis; scopes are the second axis crossing it.

{% hint style="info" %}
This page sits under **Build**, beside Integrations rather than inside it. Integrations is the catalog of other companies' apps; this is the one connector that is yours. It moved here from Settings (where it was called **SaaS Connectors**), and the old Settings address redirects. Its other tab, **Webhooks**, is where fastn calls your product back: see [Webhooks](https://docs.fastn.ai/build/saas-connectors/saas-webhooks.md).
{% endhint %}

{% hint style="warning" %}
How a scope behaves once connections exist against it (whether it can be renamed or removed with live customer connections attached) is not documented here. Register a scope you intend to keep, and confirm the behavior in your own workspace before restructuring one that is in use.
{% endhint %}


---

# 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/build/saas-connectors.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.
