How to Set Up a Static Configuration Flow?

Configuration flows in Fastn allow you to define variables, map values, and build reusable configurations that can be used in widgets or other flows.

1. 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 where you can add steps such as data mapping and field selectors.

2. Add a Data Mapping Step

• Inside the flow, add a Data Mapping Step.

• 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.

• Conditionally hide this field – Hide based on the value of another field (useful for dependent selections).

Selections Section

This is where you make the configuration dynamic:

3. Configure Static Selector

In the Options section, go to the Selection Type setting and choose Static.

The Static Configuration Flow type is used when you want to define a fixed list of options and their corresponding values manually. These options are predefined by you and appear to the user in the form of a dropdown list.

For example, if you’re defining a variable called syncFrequency in your Data Mapper step, you can configure it as an array and manually add static options.

4. Setting Up Static Options

After selecting Static as your selection type, you’ll see the same general field options available for configuration:

Each item consists of:

• Option Label – The name displayed in the UI (e.g., “Once a Day”).

• Option Value – The value stored in the backend (e.g., 24).

You can add as many static values as needed. These will appear in the configuration as a dropdown list for users to choose from.

Example: Sync Frequency Variable

Let’s say you have a variable called syncFrequency.

• When syncFrequency is an array, you can manually define options such as:

  • Option Label: Once a Day → Option Value: 24

  • Option Label: Every Hour → Option Value: 12

This will be shown to users in a dropdown list when configuring the widget.

However, if your syncFrequency depends on another variable.

For example, if the label or value needs to be generated dynamically (like HubSpotToCin7), then you should define syncFrequency as an object variable and use a Dynamic Configuration Flow instead.

Your configuration flow is now set up with Static Selection, allowing you to define fixed option values that appear in dropdown menus. These static variables can be used in widgets or other flows wherever consistent, predefined selections are needed.

When to Use Static vs. Dynamic Config Flow?

• Static Configuration Flows: Use when you want fixed dropdown options that don’t change (e.g., predefined sync frequencies or toggle options).

• Dynamic Configuration Flows: Use when your options need to be fetched dynamically (e.g., pulling tables, files, or account data).

🔗For more examples: • Custom Configuration Flow Guide • Dynamic Configuration Flow Guide