A Dynamic Dropdown allows users to select a value from a list of options that are loaded automatically from an API or external data source.

Unlike a Static Dropdown, the available options are not manually defined. Instead, they are fetched when the field is loaded.

This is useful when the available options:

• vary between accounts,

• change frequently,

• or come from another application.

Simple flow:

System fetches data from an API → Options appear in the dropdown → User selects a value

Use a Dynamic Dropdown when:

• options come from an external system,

• available values change over time,

• different users may see different options,

• or the list is too large to maintain manually.

Good examples:

Example flow:

API Request → API Response → Dropdown Options → User Selection

Open the action where you want to add the dropdown field.

Inside the Action Builder, go to the right-side panel and click on the ADD FIELD dropdown.

Choose Dropdown from the list of available field types.

Choose the Dynamic Dropdown type.

Fill in the dropdown details:

The API response must contain data that can be converted into dropdown options.

Example API response:

[...][
  {
    "id": "123",
    "name": "Website Redesign"
  },
  {
    "id": "456",
    "name": "Marketing Campaign"
  }
]

Mapping:

Result:

Enable search when the API may return a large number of options.

This allows users to quickly find the value they need.

Example:

Search Project...

Use search when:

• there are many records,

• users may not know where the option is located,

• or the list changes frequently.

Enable pagination when the API contains a large dataset.

Instead of loading everything at once, data is loaded in smaller batches.

This helps:

• improve performance,

• reduce API load,

• and speed up dropdown loading.

Pagination is commonly used when:

• thousands of records exist,

• APIs return paginated results,

• or large workspaces are supported.

Here are some common Dynamic Dropdown setups:

• Use Dynamic Dropdown when data comes from an external system

• Use meaningful labels that users can easily recognize

• Map values to unique identifiers whenever possible

• Enable search for large datasets

• Enable pagination when supported by the API

• Test option loading before publishing the action

Use a Dynamic Dropdown when the available options need to be loaded automatically from an API or external system.

It helps:

• keep data up to date,

• reduce manual maintenance,

• and provide users with real-time options from connected applications.

Remember:

Dynamic Dropdown = Options are loaded from an API → Users select from the available data