> 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/tutorials-1/understanding-flow-types/how-to-set-up-a-configuration-flow-in-fastn/setting-up-a-configuration-flow-with-static-selection-options.md).

# Setting up a Configuration Flow with Static Selection Options

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.

## **Configuring a Static Selector**

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

<figure><img src="/files/HL4t77eZa686MDS46O92" alt=""><figcaption></figcaption></figure>

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

## **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**

<figure><img src="/files/SCmtLdzDTLUv0w17PvHf" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/5o4M4a1XPVVpbsb47geF" alt=""><figcaption></figcaption></figure>

However, if your `syncFrequency` depends on another variable.

<figure><img src="/files/Oex80UGI3HFU4ktFPwNV" alt=""><figcaption></figcaption></figure>

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.

<figure><img src="/files/fCJiZ8vihl7mMtgYTptc" alt=""><figcaption></figcaption></figure>

> 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?**

<details>

<summary><strong>Static Configuration Flows</strong></summary>

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

</details>

<details>

<summary><strong>Dynamic Configuration Flows</strong></summary>

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

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fastn.ai/tutorials-1/understanding-flow-types/how-to-set-up-a-configuration-flow-in-fastn/setting-up-a-configuration-flow-with-static-selection-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.