How it works

One workflow action creates a record-aware form

Everything runs from a single HighLevel workflow action. Here is the full process, from adding the action to starting the next workflow after the recipient saves.

1. Add Generate Record Update Form

Add the action to any HighLevel workflow, at the point where you already know – or are about to create – the record that needs review.

2. Select the Object

Choose Contact, Business, Opportunity or any HighLevel Custom Object.

3. Supply the exact Record ID, or leave blank to create

Pass the exact Record ID from earlier in the workflow to update an existing record, or leave it blank so the first submission creates a new one.

4. Choose the fields the recipient can see or edit

Set Hidden, Read-only and Required Fields to define exactly what each recipient can view, change and must complete.

5. Add instructions and branding if required

Set Form Reference, rich-text Form Instructions with workflow variables, logo and favicon, file behaviour, expiry, multiple submissions and an optional redirect.

6. Use the generated form URL

Send form_url by email, SMS, WhatsApp or into another workflow step. Use form_reference to identify the form's purpose downstream.

7. Recipient opens the form with current values already pre-filled

The current record and current field structure load automatically – nothing is mapped field-by-field into the link.

8. Recipient reviews or updates it

They see exactly the fields you exposed, with current values already there.

9. Changed values save to the same record

Only what actually changed is written back. HighLevel stays the source of truth.

10. Optionally use Record Update Form Submitted

Start the next HighLevel workflow the moment a submission succeeds – including a no-change review.

Three things that keep this working as your CRM changes

Automatic pre-fill

The complete current record and its current form fields load automatically. There's no requirement to map each field individually into a URL, whether the Object has five fields or five hundred.

Automatic field order

Fields are presented according to HighLevel's current field structure and positions, rather than manually ordered in a second form builder.

Current schema

The form uses the current HighLevel field schema when it opens or reloads, so new or changed fields can appear on the same link without a rebuild.

See the full sync-with-HighLevel story →

Every generated form link has an expiry and gives temporary, controlled access to one form context – not a HighLevel login. See Security for the full access-lifecycle explanation.

See it running in your own workflow

US$15/month after trial · 14-day free trial

Start 14-day free trial