webiny-cms-bulk-actions

Create a class implementing EntriesBulkAction.Interface with loadData and processData methods, then register it via EntriesBulkAction.createImplementation with its dependencies. Webiny automatically generates the list and process background tasks plus the GraphQL mutation.

Add a ContentEntryListConfig Browser.BulkAction element with a name matching the backend action and optional modelIds. Inside the button component, call BulkActionFeature's useCase.execute with the model, PascalCased action name, where scope, and custom data.

The engine calls loadData repeatedly until it returns zero entries, so if it keeps returning the same entries the task never converges and fails at maxIterations. Exclude already-processed entries using a status transition, a boolean flag, or a per-run token stamped in processData.

GraphQL where input nests custom fields under values, but the storage layer used by loadData expects flat dotted keys like values.onSale_not. Flatten the values object in loadData before passing it to the list use case, or add constant custom-field filters backend-side.

Custom bulk actions via EntriesBulkAction are available from Webiny 6.5.0 onward, exposed through the webiny/api/cms/entry module. Earlier versions do not include this abstraction.

Inject UpdateEntryUseCase and call execute with the model, entry id, and field values nested under values, passing skipValidation: true. This prevents unrelated required or invalid fields on the entry from failing the targeted update.