Actions32
- Client Actions
- Company Actions
- Event Actions
- External Object Actions
- Invoice Actions
- Location Actions
- Product Actions
- Webhook Actions
Client → Update
AI-generatedSummary
Updates an existing client or supplier in MICE Operations by ID, sending only the fields you add under Update Fields via a PUT request to /clients/{clientId}.
Inputs
- Client ID (required) — Numeric ID of the client to update; inserted into the request URL (/clients/{id}).
- Update Fields — Collection of optional fields sent in the JSON body: Type (client or supplier), Name, Email, Phone, Phone 2, Address Line 1, Address Line 2, Postal Code, City, Country, Country ID, VAT Number, CoC Number, OIN. Only the fields you add are sent.
- Request Options — Node-level settings: batching (items per batch, interval), ignore SSL issues, proxy, and request timeout (default 10000 ms).
Output shape
The API's JSON response for the PUT request, presumably the updated client record. The node does not transform it.
Authenticates with the miceoperationsApi credential against https://api.miceoperations.com/api/v1. The Type field in the collection defaults to 'client' when added, so adding it without changing it will set the record to client. The source does not define the response body shape.
Examples
Example 1: Correct a client's contact details after a CRM change
Client ID = 123; Update Fields: Email = new@example.com, Phone = +31 20 123 4567
Example 2: Reclassify a client as a supplier
Client ID = 45; Update Fields: Type = Supplier
Example 3: Update billing identifiers
Client ID = 77; Update Fields: VAT Number, CoC Number, Postal Code, City