Update Customer

magento.update_customer
ActionBusiness appsconnection required

Calls the Magento API with the connection's credentials.

Replace a customer account with the entity you supply. Magento's save is a replacing write, so send the whole customer with your changes applied.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Magento
Secret shape
the integration access token, or {"access_token": "…"}
Config it needs
base_url, store_code
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
customer_id
The customer's entity id.
stringYes——1
customer
The full customer entity to save, normally the object from magento.get_customer with your edits applied.
objectYes—≥ 1 characters—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "customer_id": "1"
}

Output

One shape.

result

FieldTypeExample
id
The customer's entity id.
number—
email
The customer's email address.
string—
firstname
The customer's first name.
string—
lastname
The customer's last name.
string—
group_id
The customer group the account belongs to.
number—
website_id
The website the account was created on.
number—
store_id
The store view the account was created on.
number—
created_at
When the account was created, in the store's timezone.
string—
addresses
The customer's saved addresses.
array—
custom_attributes
Any EAV attributes the store added to customers.
array—
{
  "addresses": [],
  "created_at": "",
  "custom_attributes": [],
  "email": "",
  "firstname": "",
  "group_id": 0,
  "id": 0,
  "lastname": "",
  "store_id": 0,
  "website_id": 0
}

See Update Customer run in a workflow.

In a technical demo we add the Magento connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.