Update Customer

paddle.update_customer
ActionBusiness appsconnection required

Calls the Paddle API with the connection's credentials.

Change a customer's email, name, locale, status or custom data.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Paddle
Secret shape
the Paddle API key (pdl_…), or {"api_key": "…"}
Config it needs
environment, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

6 fields, 1 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 id, prefixed ctm_.
stringYes———
email
New email address.
stringNo———
name
New full name, up to 1024 characters.
stringNo—≤ 1024 charactersSam Miller
locale
New IETF BCP 47 locale.
stringNo———
status
Set to archived to retire the customer, or active to restore them.
stringNo—one of "active", "archived"—
custom_data
Replacement key-value data for the customer (JSON).
objectNo———
  • At least one of name, email, locale, status, custom_data must be set.

Example configuration

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

{
  "name": "Sam Miller"
}

Output

One shape.

result

FieldTypeExample
id
The customer id, prefixed ctm_.
string—
name
Customer's full name, or null.
string—
email
Customer's email address.
string—
status
active or archived.
string—
locale
IETF BCP 47 locale used for their checkout and receipts.
string—
marketing_consent
Whether they opted in to marketing.
boolean—
custom_data
Your own key-value data, or null.
object—
created_at
RFC 3339 creation timestamp.
string—
{
  "created_at": "",
  "custom_data": {},
  "email": "",
  "id": "",
  "locale": "",
  "marketing_consent": false,
  "name": "",
  "status": ""
}

See Update Customer run in a workflow.

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