# How to Set Up a Configuration Flow in Fastn? Configuration flows define how data, fields, and user inputs are structured and connected inside your widgets. They help you build configurable interfaces that pass values dynamically between user inputs and connected apps or flows. With configuration flows, you can: * [x] Create reusable configuration interfaces for widgets or other flows. * [x] Define and manage variables that drive your integrations. * [x] Add logic for static, dynamic, custom, or mapping-based selections. * [x] Apply validation to enforce input formats and required fields. ## **Creating a Configuration Flow** To create a configuration flow: * Go to the **Widgets** section in Fastn. * Click the arrow next to the **Add Widget** button (top-right corner). * Select **Add Configuration Flow**.

* Enter a name for your configuration flow and click **Build**.

This creates a configuration flow that allows you to add steps, such as data mapping and field selectors. This opens the flow builder, where you can start adding steps such as: * **Data Mapping** to define fields and variables. * **Connectors or Actions** to link with external tools. * **Advanced Controls**, like conditions, transformations, and loops. Once your flow is created, you can define how users will interact with it through field configuration. ## **Adding and Configuring Fields** * Inside the flow, add a **Data Mapping Step**.

The **Data Mapper** defines the variables and parameters that will be dynamically passed into your target app or flow. * Click the three dots on this step to access options: * **Advanced Action** * **Add Parent Key** * **Set Default Value** * **Options** The **Options** setting lets you configure fields that support **labels, selectors, and values**.

* Configure the following sections: ### **General Section** Define how this field behaves and appears in the configuration pop-up:

* **Label** – Sets the display name in the widget UI. * **Disable this field** – Prevents user edits. * **Mark as new ID field** – Assigns a unique identifier for the configuration. * **Hide this field in configuration pop-up** – Keeps advanced fields hidden from the user. * **Hide Based on config field** – Control a field’s visibility based on another field’s value, by defining a key, operation, and value condition that determines when the field should appear or stay hidden.

### **Selections Section** This is where you make the configuration dynamic: ## **Selecting a Field Type** Every field supports **Selections**, which define how users choose or input values.\ You can choose one of four **Selection Types**, each suited to different use cases.

		Cover image
Static Selection	Define fixed, predefined options that users can pick directly from a dropdown.	Screenshot 2025-10-16 232357.png	setting-up-a-configuration-flow-with-static-selection-options	setting-up-a-configuration-flow-with-static-selection-options
Dynamic Selection	Fetch real-time data from connected flows or APIs to populate your fields dynamically.	Screenshot 2025-10-16 232457.png		setting-up-a-configuration-flow-with-dynamic-selection-options
Custom Selection	Design fully tailored configuration experiences like file pickers or advanced selectors.	Screenshot 2025-10-16 232656.png		setting-up-a-configuration-flow-with-custom-selection-options
Mapping Selection	Map fields and values between source and destination flows for seamless data alignment.	Screenshot 2025-10-16 232812.png		setting-up-a-configuration-flow-with-mapping-selection-options

Each selection type has its own setup flow and example.\ You can learn more in the following guides: ### **Adding Field-Level Validation** You can also add validation to ensure users provide correct data before saving their configurations.\ For example, you can: * [x] Require fields to be filled. * [x] Enforce URL or email formats. * [x] Display custom error messages for invalid input. Learn more about how to add field validation here:

		Cover image
Fields Level Validation in Configuration Flows	Add rules to verify user input and ensure data accuracy in configuration fields.	Screenshot 2025-10-16 232116.png	setting-up-field-level-validation-in-configuration-flows

## **Using Configuration Flows in Widgets** Once configured, your flow can be attached to any widget: * The widget automatically renders the fields you’ve defined. * Static, dynamic, or mapped options appear in dropdowns or pickers. * Any validation rules are enforced before submission. > This enables your widgets to provide users with rich, reliable, and interactive configuration experiences, powered by your underlying flow logic. ### **Next Steps** {% stepper %} {% step %} Explore each configuration type in detail. {% endstep %} {% step %} Combine mapping and validation for complex use cases. {% endstep %} {% step %} Reuse your configuration flows across multiple widgets to maintain consistency. {% endstep %} {% endstepper %}