Skip to main content
Use the platform Update User Details tool to save information collected during a conversation. For the GoHighLevel workflow described here, the account needs a working GoHighLevel connection and the conversation must resolve to the correct contact. This companion explains the product workflow. The developer-authored Platform tools reference remains the reference for API attachment.

​
Set up contact updates

  1. Open Assistants, select your assistant, and open Tool Kit → Tools & APIs.
  2. Find Update User Details (update_user_details) and add it to the assistant. Confirm it appears under Assigned to this assistant.
  3. Tell the assistant which information to collect and when to confirm it. For example:
    Confirm the customer’s name and email. If either is missing or incorrect, ask for the correction, repeat it back, and use Update User Details to save the confirmed information. Do not say it was saved if the tool reports a failure.
  4. Save and publish the assistant.
  5. Test with a dedicated GoHighLevel contact and a conversation linked to that contact.

​
What can be updated

Supported contact fields include name, email, phone, company, street address, city, state, postal code, country, website, and timezone. Custom fields require a valid field mapping; the name of an arbitrary prompt variable does not create a CRM field. Use the field definitions shown in the tool. For custom integrations, supported aliases include first_name, last_name, phone_number, address, and postal_code. The full address workflow is covered in Save an address.

​
Supported contact fields

For custom calls to update_user_details, these are the accepted field names. Use the first name listed as the canonical field; the remaining names are aliases for the same value. If multiple aliases are supplied, the first available nonempty value in the listed order wins. Missing, null, and empty-string values are skipped; they are not instructions to clear a field. The custom-fields value must use valid GHL field identifiers and the structure required by that field. A prompt variable name is not a field identifier.

​
Verify the saved record

Open the intended GoHighLevel contact after the test. Confirm every requested value, then inspect the conversation’s tool result if a value is missing. Also confirm the corresponding contact in Assistable when later steps, such as booking, depend on its email or phone. A tool response can report a failure even when the HTTP request itself returned successfully. Invalid email or phone values can be rejected while other valid details are saved. Ask for a corrected value and verify that specific field again.

​
Troubleshooting

  • No linked contact: collect the contact’s identity before retrying; do not substitute a different customer’s ID.
  • Connection or token error: reconnect the correct GoHighLevel location and retest.
  • Wrong or missing field: confirm the tool’s supported parameter and custom-field mapping.
  • Contact appears merged: check the surviving contact when the submitted email or phone already belongs to another record.

​
When a custom tool is useful

Use a custom endpoint only when you need a different CRM or a business-specific transformation. A proxied custom tool carries the contact identity in meta_data.contact_id when it is available; your receiver must validate that identity and account before writing. See Connect a custom API tool.