This documentation provides a reference to the updateCollectionsWorkflow
. It belongs to the @medusajs/medusa/core-flows
package.
This workflow updates one or more collections. It's used by the Create Collection Admin API Route.
This workflow has a hook that allows you to perform custom actions on the updated collections. For example, you can pass under additional_data
custom data that
allows you to update custom data models linked to the product collections.
You can also use this workflow within your own custom workflows, allowing you to wrap custom logic around product-collection update.
Source CodeWorkflow hook
Step conditioned by when
View step details
UpdateCollectionsWorkflowInput
UpdateCollectionsWorkflowInputselector
FilterableProductCollectionPropsadditional_data
Record<string, unknown>Optionaladditional_data
property in HTTP requests.
Learn more in this documentation.ProductCollectionDTO[]
ProductCollectionDTO[]id
stringtitle
stringhandle
stringcreated_at
string | Dateupdated_at
string | Datedeleted_at
string | DateOptionalHooks allow you to inject custom functionalities into the workflow. You'll receive data from the workflow, as well as additional data sent through an HTTP request.
Learn more about Hooks and Additional Data.
This hook is executed after the collections are updated. You can consume this hook to perform custom actions on the updated collections.
Handlers consuming this hook accept the following input.
input
inputadditional_data
Record<string, unknown> | undefinedadditional_data
property in HTTP requests.
Learn more in this documentation.collections
ProductCollectionDTO[]This section lists the events that are either triggered by the emitEventStep
in the workflow, or by another workflow executed within this workflow.
You can listen to these events in a subscriber, as explained in the Subscribers documentation.
Event | Description | Payload | Action |
---|---|---|---|
| Emitted when product collections are updated. |
|