Prefill links
Build the encrypted personalised link — and why old-style links no longer work.
Prefill record ids are not put in the URL directly. That would expose the id and let someone swap it for another record's.
Instead, all your Data Mapping parameters are packed into one encrypted, tamper-proof token carried
by a single data parameter, and the form is named by its Form Key:
…/forms?f=<form key>&data=<token>
Building the token
For a step-by-step Flow recipe, see Build a personalised link. What follows is the contract itself.
Use the Build Flux Forms Prefill Link action from a Flow — typically the Flow that sends the invitation email. Its inputs:
- Form Id — the form the link targets.
- Parameter Names and Record Ids — two matching lists. For each Data Mapping parameter name (for
example
leadId), put the record id it should carry in the same position of the Record Ids list. - Valid For (Days) (optional) — how long the link stays usable. Leave it blank for a link that never expires.
It returns the Relative URL (?f=…&data=…) to append to your Experience Cloud form page, and the
raw Token.
Fail-closed behaviour
Tampering with the token, using it on a different form, or using it after it expires simply drops the prefill. The form still loads — just empty. Nothing leaks and nothing errors.
Treat a link like a password
Anyone who has the link sees the values it carries. Two habits follow:
- Set Valid For (Days) on links you send out, so they stop working after a while.
- Do not paste a personalised link into a shared channel or a ticket.
Old links no longer work
Changed behaviour. The form link now uses the Form Key (
?f=<form key>), not the form's record id, and prefill must use the encrypteddatatoken.These no longer work and must be regenerated with the Build Flux Forms Prefill Link action:
- links using
?form=<id>- links with a raw record id in the URL, for example
…?leadId=00Q…- presetting a field straight from the link with
?<field key>=value— that un-tokenised path was removed entirelyUse Data Mapping plus the token instead.
