## What are Search Params?

Search params are URL query parameters available inside the interface at render time. Use them to pass data between views, between buttons, or from external sources via the URL.

## Passing Params

### Via Action Button

1. Add a **Button** block and set **Button Type** to **Action Button**.
2. Set **Action Type** to **go to view** and pick the target view from the **View Name** dropdown.
3. Click **Handle params** under **Parameters** and add key / value pairs.
4. Values support the Data Picker, so you can pass dynamic data like `{{deal.id}}`.

### Via Navbar Link

1. Add a **Navbar** block, click **Manage Links**, and add or edit a link.
2. Set **Link Type** to **Interface** and pick the target view from **Target Interface**.
3. In the link's **Parameters** section, click **Add Parameter** to append key / value rows. Values support the Data Picker.

### Via Table Action Column

A Table action column's per-action settings include a **Params** key / value editor. Each row's data plus those params are forwarded as search parameters when the action is clicked.

### Via Form Submission

There are two ways a form can pass values as search params on the navigation that follows submission.

**Wait for response or JSON / Multipart-Form-Data with Select view**

1. Configure a **Form Submit Button** with **After submission** set to **Select view** (and Form Type **JSON** or **Multipart/Form-Data**).
2. Optionally add explicit **Parameters** rows -- key / value pairs sent alongside.
3. Turn on **Use input values as search params** to also forward every form input value as a search parameter on the navigation. Each input's internal `name` becomes the parameter key, and the user-entered value becomes the value.

**Open view with form data**

1. Set **Form Type** to **Open view with form data** on the submit button.
2. The Submit URL and After submission settings hide; submission no longer makes an HTTP request.
3. On submit, every form input value is forwarded to the chosen view as a URL search parameter and the navigation runs immediately. Useful for multi-step wizards or filter views.

### Via URL Button

URL Buttons that open a custom URL or another OneClick interface let you append query parameters to the request:

1. Click the **Button URL** button on the URL Button settings to open the **URL Configuration** dialog.
2. In the **Query Parameters** card click **Add Parameter** and fill in key / value pairs. Values support the Data Picker.
3. The pairs are appended to the target URL when the button is clicked.

## Accessing in Data Picker

1. Open any Data Picker field.
2. Switch to the **searchparams** tab (icon-only -- the link icon, with tooltip `searchparams`).
3. Click a parameter to insert it. The chip compiles to a `{{searchparams.<key>}}` placeholder at render time.

The list inside the tab shows every search parameter currently present on the URL plus any that have been declared as expected by buttons elsewhere in the interface (so you can bind to them before they actually arrive).

<img
  src="https://res.cloudinary.com/zimple/image/upload/f_auto,q_auto/v1777464894/interface-docs/data-picker-searchparams.png"
  alt="Builder canvas with a Title block selected. The Data Picker popup is open below the block on the searchparams tab (the link icon highlighted in the icon-only tab strip at the top), showing two pill-shaped parameters 'param_1' and 'param_2' under a search input."
  width="1440"
  height="900"
  loading="lazy"
/>