# Custom elements

## Buttons, inputs, and dropdowns

Figma doesn’t have built-in element types for [buttons](/~/changes/1032/core-resources/elements/visual-elements.md#button), [inputs](/~/changes/1032/core-resources/elements/input-forms.md#input), [multiline inputs](/~/changes/1032/core-resources/elements/input-forms.md#multiline-input), or [dropdowns](/~/changes/1032/core-resources/elements/input-forms.md#dropdown).

To help improve conversion accuracy, the Deezign plugin includes a **Buttons/Inputs** tab. Here, you can tag a selected node as a button, input, dropdown, or multiline input before converting.

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

Keep in mind:

* Only nodes with **one child or fewer** can be converted to a button, input, or dropdown, since Bubble doesn’t allow icons inside these elements.
* Nodes with **up to two children** can be converted to dropdowns to support a label plus a down chevron.


---

# Agent Instructions: 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:

```
GET https://manual.bubble.io/~/changes/1032/help-guides/design/importing-from-figma/custom-elements.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.