Contact Update Records with Forms
We're reachable however you prefer to ask.
Looking for a quick answer instead? Check the FAQ or the full Documentation.
Online chat
For fastest response, use the online chat widget.
Phone
HighLevel Workflow Implementation Session
Bring your workflow scenario. We'll look at the records and data involved, work out the best form setup, and help you implement it in HighLevel.
Common issues
Form link will not open the form
The recipient is shown a specific message explaining why: link not recognised, link expired, form already submitted, CRM record no longer exists, app connection unavailable, Object unavailable, HighLevel connection needs attention, or a rate limit was temporarily reached. Match the message to the checks below, and confirm the link was copied in full.
Missing field
Confirm the field isn't set to Hidden, and that the field type can be displayed – unsupported field types are omitted rather than guessed.
Submission fails
If the specific field being saved was also changed in HighLevel after the form was opened, that field is highlighted in place with the current value and what was entered, rather than the submission being overwritten. No reload is needed and nothing else on the form is lost — a change to a different field elsewhere on the record has no effect on the submission at all.
File upload problem
Check whether the upload actually completed, whether the file type or size was accepted, and whether a Required file field would be left empty. For create-mode records, a deferred file upload can fail even though the record itself was created. A successful upload refreshes that form's own conflict-detection baseline, so uploading then saving on the same form load does not itself trigger a conflict message. In Replace mode, check for overlapping edits from a different session – if someone else's edit to the record (a save or upload on a different copy of the link) lands in between, the next Save from this session is blocked with a record-conflict message, the same protection that applies to any other field.
Submitted workflow did not run
Confirm the workflow is listening for the Record Update Form Submitted trigger, and that the submission actually completed (including a no-change review, which still fires the trigger).
Objects or fields missing in workflow builder
All HighLevel Custom Objects available in that account are supported – confirm the Object actually exists in that specific HighLevel account and location.
When you contact us, please include
- Form ID
- Object (Contact, Business, Opportunity or Custom Object name)
- Create or update mode
- Workflow name
- Form Reference
- The exact visible error
- Approximate date/time
- Affected field
- Whether a fresh form reproduces it