This documentation provides a reference to the updateCartWorkflow
. It belongs to the @medusajs/medusa/core-flows
package.
This workflow updates a cart and returns it. You can update the cart's region, address, and more. This workflow is executed by the Update Cart Store API Route.
This workflow has a hook that allows you to perform custom actions on the updated cart. For example, you can pass custom data under the additional_data
property of the Update Cart API route,
then update any associated details related to the cart in the workflow's hook.
You can also use this workflow within your customizations or your own custom workflows, allowing you to wrap custom logic around updating a cart.
Source CodeWorkflow hook
Step conditioned by when
View step details
UpdateCartWorkflowInput
UpdateCartWorkflowInputid
stringpromo_codes
string[]Optionalregion_id
stringOptionalcustomer_id
null | stringOptionalsales_channel_id
null | stringOptionalemail
null | stringOptionalcurrency_code
stringOptionalmetadata
null | Record<string, unknown>Optionaladditional_data
Record<string, unknown>Optionaladditional_data
property in HTTP requests.
Learn more in this documentation.Hooks 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 before all operations. You can consume this hook to perform any custom validation. If validation fails, you can throw an error to stop the workflow execution.
Handlers consuming this hook accept the following input.
input
inputinput
objectcart
anyThis hook is executed after a cart is update. You can consume this hook to perform custom actions on the updated cart.
Handlers consuming this hook accept the following input.
input
inputcart
anyadditional_data
Record<string, unknown> | undefinedadditional_data
property in HTTP requests.
Learn more in this documentation.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 a cart's details are updated. |
| |
| Emitted when the cart's region is updated. This
event is emitted alongside the |
|