VitePOS BridgeInstall

Summary

Updates an existing VitePOS customer by sending a PATCH to the bridge endpoint /wp-json/vtab/v1/customers/{Customer ID} on the WordPress site from the credentials, with fields supplied via UI fields or a raw JSON body.

Inputs

• Customer ID (required) — ID of the customer to update; inserted into the request URL path.
• Input Mode — 'Use Fields' (default) builds the body from Customer Fields; 'Advanced JSON' sends the JSON Body as-is.
• Customer Fields — Collection (Use Fields mode). Only filled values are sent: id, external_id, email, first_name, last_name, phone, company, address_1, address_2, city, state, postcode, country. Dry Run, if true, adds dry_run: true to the body.
• JSON Body — Advanced mode only. Raw request body (default {"dry_run": true}); must be valid JSON or the node errors. In this mode Customer Fields are ignored.

Output shape

One item per input item: the bridge's JSON response with an added human-readable 'response' string (e.g. 'Customer 123 updated.'), or 'Customer update completed.' if no ID is in the reply.

If the API response is not an object or already has a 'response' key, it is nested under 'raw'. If the API returns status/success false, 'response' holds its message. With Continue On Fail, failed items return {error: message}. Empty bodies are not sent, so selecting no fields sends a PATCH with no body.

Examples

Example 1: Update a customer's phone and city after a form submission

Resource: Customer; Operation: Update Customer; Customer ID: {{$json.customerId}}; Input Mode: Use Fields; Customer Fields: Phone, City.

Example 2: Preview a change without saving it

Customer ID set; Customer Fields: Email plus Dry Run enabled.

Example 3: Send a custom payload

Input Mode: Advanced JSON; JSON Body: {"company":"Acme","dry_run":false}.

Links

• n8n community nodes installation guide