Update Customer
chargebee.update_customer
ActionCRM & salesconnection required
Calls the Chargebee API with the connection's credentials.
Change one or more attributes of an existing customer.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Chargebee
- Secret shape
- the site API key: the raw string, {"api_key": "…"}, or the HTTP Basic pair {"username": "<api key>", "password": ""}
- Config it needs
- site, base_url
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
customer_id The Chargebee customer id. | string | Yes | — | — | — |
fields The attributes to change, as a JSON object using Chargebee's own names, e.g. {"email": "new@acme.io", "auto_collection": "off"}. Attributes left out keep their current value. | object | Yes | — | ≥ 1 characters | {"auto_collection":"off","email":"new@acme.io"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": {
"auto_collection": "off",
"email": "new@acme.io"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
customer The customer resource exactly as Chargebee returned it. | object | — |
card The customer's card, present only when one is on file. | object | — |
{
"card": {},
"customer": {}
}Notes
- The Chargebee site and API key come from the connection; every path below is relative to https://<site>.chargebee.com/api/v2.
- POST /customers/{customer-id}
See Update Customer run in a workflow.
In a technical demo we add the Chargebee connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.