> 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/choose-integrations.md).

# Step 2: Choose integrations

Onboarding step 2. Choose the integrations your customers get inside your product, and build the first one.

This step is for choosing the integrations your customers get inside your product, and building the first one. You pick a system your customers use and say what the integration should do; fastn's agent (**Build with AI**) builds it. An integration is a connector, a connection, its triggers and the workflow logic around them: it moves data between your product and the customer's system and does a job there.

**Why:** customers ask for integrations as jobs, not connectors. Not "a HubSpot connector", but "when a shipment is created, add it to our HubSpot". What you choose here is what they find in your widget.

### Without fastn and with fastn

|                              | Without fastn                                                                                   | With fastn                                                                                                                                           |
| ---------------------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Building it                  | Engineers learn the other system's API, then write the sync, sign-in, retries and field mapping | Describe the job in a sentence; Build with AI or your AI tool builds and tests it                                                                    |
| Another system               | A new engineering project                                                                       | Pick it from the catalog, or have its connector built as in [step 1](https://docs.fastn.ai/get-started/onboarding/connect-your-product.md)           |
| Running it                   | Your own queues, schedules and logs                                                             | fastn runs and logs every workflow, per customer                                                                                                     |
| Different needs per customer | Custom code per customer                                                                        | Each customer adjusts mappings and filters in the widget ([step 4](https://docs.fastn.ai/get-started/onboarding/customers-connect-and-customize.md)) |

### What it's made of

| Component              | What it is                                                                                                                        | Example                             |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------- |
| Connectors             | Your product's connector and the customer's system's connector                                                                    | Your product and HubSpot            |
| Workflow               | The code that reads, transforms and writes data                                                                                   | Turn a shipment into a HubSpot deal |
| Trigger                | What starts the workflow: an event in a connected system, a webhook, or a schedule                                                | A shipment is created               |
| Configuration template | The default field mappings and rules each customer starts from                                                                    | Shipment status → deal stage        |
| Test cases             | Checks Build with AI runs before publishing                                                                                       | One deal per shipment               |
| Versions               | Publishing saves a numbered copy you can go back to; deploying sends it to Test (to try it) or Live (where it runs for customers) | v3 in Live                          |

### Ways to do it

| Way             | Best when                                                           | What you do                                                                                                                                                                            |
| --------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Build with AI   | You want it built and tested for you                                | Describe the job, or pick a suggested use case. Review the plan, answer its questions, approve the mappings and tests. Uses AI credits                                                 |
| Your AI tools   | Your team works in Claude, ChatGPT, Cursor or similar               | Describe the job in your AI tool through fastn's MCP server, and approve each step in the chat                                                                                         |
| Connectors only | Customers only need to connect a system your own code or agents use | Add the connector to the widget, with no workflow                                                                                                                                      |
| Unified API     | Customers use different systems for the same job                    | Add a category such as CRM: one "create contact" call works with HubSpot, Salesforce or another CRM                                                                                    |
| Whole catalog   | Self-serve products, or you don't know yet what customers need      | Turn on **Catalog connectors** in the widget builder, and build integrations later                                                                                                     |
| By hand         | You want full control                                               | Create the workflow and trigger, then add it to the widget. Code editing is off by default (fastn turns it on per organization), so until then you change code by asking Build with AI |

### Use cases and scenarios

| Use case         | Example                                                                | Trigger                 | Scope              |
| ---------------- | ---------------------------------------------------------------------- | ----------------------- | ------------------ |
| Push events out  | A shipment created in your product is added to the customer's HubSpot  | Event from your product | Organization level |
| Pull data in     | The customer's Jira issues are imported into your product              | Schedule                | Organization level |
| Notifications    | A message goes to the customer's Slack when something critical happens | Event from your product | Organization level |
| Personal systems | Meetings booked in your product go to each user's own Google Calendar  | Event from your product | User level         |

### Scope: shared or per user

Each integration has a **Scope** setting: who shares a connection inside one customer. Either way, each customer's connections stay separate, as long as each embed token is minted for that customer.

|                    | Organization level                                 | User level                  |
| ------------------ | -------------------------------------------------- | --------------------------- |
| One connection for | The whole customer, shared by its users            | Each user at a customer     |
| Typical systems    | CRM, project tool, data warehouse, shared channels | Their own email or calendar |

### In the onboarding

Onboarding suggests systems for your product, each marked **Ready** or **Needs a connector** (fastn has none for that system yet, so one is built first). Pick one, then a suggested use case or your own in a sentence, and watch the **fastn agent** build the connector, workflow, trigger, widget entry and connection. It answers its own questions with assumptions you confirm. Or enable the whole catalog and build later. Finishing the step earns 10 AI credits.

<figure><img src="https://1255842839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3iSr2Tx8FvvuoLPncziH%2Fuploads%2Fgit-blob-85a7821290de2bb25ab53805e8a2b001576776ba%2Fonboarding-step-2-choose-integrations.webp?alt=media" alt="Onboarding step 2 of 4, Pick your first integration: Jira, Slack and GitHub marked Ready, DefectDojo and Vanta marked Needs a connector, with Enable the whole fastn catalog and Skip this step"><figcaption><p>Step 2: Pick your first integration.</p></figcaption></figure>

### Related docs

[Build with AI](https://docs.fastn.ai/build/agent.md) · [Creating a workflow via AI](https://docs.fastn.ai/build/agent/creating-a-workflow-via-ai.md) · [Workflows](https://docs.fastn.ai/build/integrations/workflows.md) · [Triggers](https://docs.fastn.ai/build/integrations/triggers.md) · [Unified APIs](https://docs.fastn.ai/build/integrations/unified-apis.md) · [Understanding tenancy](https://docs.fastn.ai/embed/embedding/understanding-tenancy.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/choose-integrations.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.
