ghl_object_update_record
Update a custom object record by ID for a given location and schema key, sending field values in the request body. Use it to change existing record properties through the GoHighLevel API.
Instructions
SPEC GAP: UpdateCustomObjectRecordDto is an empty object schema in v3/objects-v3.json — verified against the raw spec, not an extraction bug. The body property will accept arbitrary JSON; GHL's convention (per external docs linked from this op, not confirmed in this corpus) is a properties object keyed by the object's field keys.
Update Record
Update a Custom Object Record by Id. Supported Objects are business and custom objects. Documentation Link - https://doc.clickup.com/8631005/d/h/87cpx-277156/93bf0c2e23177b0/87cpx-376296
Endpoint: PUT /objects/{schemaKey}/records/{id} (Version header: v3; source: v3/objects-v3.json)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"schemaKey": "<schemaKey>",
"id": "<id>",
"locationId": "<locationId>",
"body": "<body>"
},
"name": "ghl_object_update_record"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | id of the record to be updated. Available on the Record details page under the 3 dots or in the url | |
| body | Yes | Request body (schema carried verbatim from the official OpenAPI spec). | |
| schemaKey | Yes | The key of the Custom Object / Standard Object Schema. For custom objects, the key must include the “custom_objects.” prefix, while standard objects use their respective object keys. This information is available on the Custom Objects Details page under Settings. | |
| locationId | Yes |