umbraco-collection-action

You add a custom button to the Umbraco backoffice collection toolbar by registering a collectionAction manifest with an alias, label, and API entrypoint, then implementing an action class extending UmbCollectionActionBase to define its execute() or getHref() behavior.

Conditional rendering for Umbraco collection actions uses Umb.Condition.* patterns tied to collection aliases, ensuring the toolbar button appears only when the extension registry matches the specific collection being viewed in the backoffice.

Yes, you can use modal dialogs for Umbraco collection action workflows by opening and coordinating modal dialogs within your action class, enabling interactive flows such as exports or multi-step user input directly from the toolbar button.

In Umbraco extension actions, execute() runs code-based logic for collection-level operations, while getHref() returns a navigation URL for link-based behavior, allowing you to choose between programmatic workflows or direct page redirects.

TypeScript is used to implement collection actions in the Umbraco extension registry, providing the typed class structure needed to extend UmbCollectionActionBase and properly wire manifests, conditions, and API entrypoints for backoffice integration.