Skip to main content

Fill the controls that are not plain inputs.

Modern forms use comboboxes, date pickers, and rich-text editors. FillMatic opens them, picks an option, and confirms it like a user, so your app state stays in sync.

Step by step

What FillMatic does for you

  1. 01

    ARIA widgets

    Comboboxes, listboxes, date pickers, switches, sliders, and radio groups, including Radix and shadcn/ui components.

  2. 02

    Rich-text editors

    Text goes in through the editor itself, so ProseMirror, Tiptap, Lexical, Slate, Quill, and Trix keep their document model in sync.

  3. 03

    Recipes for the rest

    Record the clicks a custom control needs once in the side panel. The Recipe replays those steps on every matching fill, with no custom JavaScript.

Also useful

The details

Frames and shadow DOM

Supported fields inside iframes and open shadow roots are filled too. Saved Actions fill child frames only when you opt in.

One failure does not stop the run

If a widget will not cooperate, FillMatic skips it, keeps filling, and lists it in the fill summary with a reason.

Recipes run first

A Recipe drives its widget before anything else is filled, and generic filling leaves that widget alone for the rest of the run.

File inputs, closed shadow DOM, and browser-owned pages are not supported. How Recipes work.

Try it on your own form.

Install FillMatic, open the form you test most, and run your first fill. The common case needs no setup.

Add to Chrome