# Control Panels: Wiring

> Connecting a widget to data or an action.

Glider documentation · Logic · Web page: https://cgglider.com/docs/control-panels/wiring/

Sections of this page: [Building a panel](https://cgglider.com/docs/control-panels.md) · [Widgets](https://cgglider.com/docs/control-panels/widgets.md) · [Wiring](https://cgglider.com/docs/control-panels/wiring.md) · [Operating a panel](https://cgglider.com/docs/control-panels/runtime.md)

An input widget writes its value to its target path, and any graphic bound to that path follows. A button is different: it can write a value, fire a named event, and carry an ordered list of actions.

The action picker offers both families in one surface, because “what does this button do?” should have one answer:

| Family | Examples |
| --- | --- |
| Unit actions | Start this clock · Reset that counter · Refresh a poller · Next on a ticker. |
| Animations | Play a workflow. |

> **Note:** The list is ordered, and a press runs all of it — an operator's “take” is usually more than one thing. The unit action catalog is read straight from the resolvers, so a new unit kind appears in the picker as soon as its resolver is registered.