REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools

Actions38

Customers → Update

AI-generated

Summary

Updates an existing LatePoint customer by sending a PUT request to /customers/{id} with either individual fields or a custom JSON/form body.

Inputs

  • ID (required) — ID of the customer to update; appended to the endpoint path.
  • Send Body — When on, the request body comes from JSON Body or Form Data and Additional Fields is ignored. Default off.
  • Body Content Type — Shown when Send Body is on. Choose JSON or Form Data. Form data is still sent as a JSON object of name/value pairs.
  • JSON Body — JSON object used as the request body when Send Body is on and the content type is JSON. Invalid JSON throws an error.
  • Form Data — Name/value parameter list, converted into a JSON object body when Send Body is on and the content type is Form Data.
  • Additional Fields — Used when Send Body is off. For customers, the options are First Name, Last Name, Email, Phone. Only the fields you add are sent. Their defaults are $fromAI expressions, so an AI agent fills them in.
  • Description — Free-text prompt or context for AI use. The source does not use it in the request.

Output shape

A single item containing the updated customer record. This is the data property of the API response when present, otherwise the full response.

The request is sent with Bearer API key authentication to the base URL from the credentials. With Continue On Fail, errors are returned as an item with an error message. If Send Body is on and the body is empty, no body is sent.

Examples

Example 1: Change a customer's email and phone number

Resource: Customers, Operation: Update, ID: 42, Send Body off, Additional Fields: Email = new@example.com, Phone = +1 555 0100

Example 2: Update a customer from a custom payload built earlier in the workflow

ID: {{$json.customer_id}}, Send Body on, Body Content Type: JSON, JSON Body: {"first_name":"Ana","last_name":"López"}

Links

Discussion