This documentation provides a reference to the updateCustomersWorkflow
. It belongs to the @medusajs/medusa/core-flows
package.
This workflow updates one or more customers. It's used by the Update Customer Admin API Route and the Update Customer Store API Route.
This workflow has a hook that allows you to perform custom actions on the updated customer. For example, you can pass under additional_data
custom data to update
custom data models linked to the customers.
You can also use this workflow within your customizations or your own custom workflows, allowing you to wrap custom logic around updating customers.
Source CodeWorkflow hook
Step conditioned by when
View step details
UpdateCustomersWorkflowInput
UpdateCustomersWorkflowInputselector
FilterableCustomerPropsupdate
CustomerUpdatableFieldsadditional_data
Record<string, unknown>Optionaladditional_data
property in HTTP requests.
Learn more in this documentation.CustomerDTO[]
CustomerDTO[]id
stringemail
stringhas_account
booleandefault_billing_address_id
null | stringdefault_shipping_address_id
null | stringcompany_name
null | stringfirst_name
null | stringlast_name
null | stringaddresses
CustomerAddressDTO[]phone
null | stringgroups
object[]metadata
Record<string, unknown>created_by
null | stringdeleted_at
null | string | Datecreated_at
string | Dateupdated_at
string | DateHooks 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 customers are updated. You can consume this hook to perform custom actions on the updated customers.
Handlers consuming this hook accept the following input.
input
inputcustomers
CustomerDTO[]additional_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 customer is updated. |
|