Build a personalised link
Use the Build Flux Forms Prefill Link action in a Flow to mint a link that fills the form in for one person.
A personalised link carries an encrypted token so a visitor arrives at a form that already knows who they are. You cannot type one by hand — the token is generated — so you build it in a Flow using the Build Flux Forms Prefill Link action.
Read Data mapping first: the link can only carry parameters the form's data mapping actually declares, and it can only fill fields a Purpose grants read access to.
Before you start
- The form has Data Mapping bindings, each with a URL parameter name (for example
leadId). - A Purpose grants read access to the fields being prefilled, and is assigned to the form.
- The form is Active.
- An administrator has set the Site Base URL in CMS Media Settings.
The action
Add it to a Flow as Action → Build Flux Forms Prefill Link.
Inputs
| Input | Type | Notes |
|---|---|---|
| Form Id | record Id | The Form record the link targets. Not the Form Key — the record Id. |
| Parameter Names | text collection | The data-mapping parameter names, e.g. leadId. |
| Record Ids | text collection | The record Id each parameter carries. |
| Valid For (Days) | number | Optional. Leave blank for a link that never expires. |
Outputs
| Output | Use it for |
|---|---|
| Relative URL | the query string to append to your site page: ?f=…&data=… |
| Token | the raw token, if you are assembling the URL yourself |
| Success | whether the link was built. Check this. |
| Error Message | what went wrong when it was not |
Parameter Names and Record Ids are index-paired. The first name gets the first Id, the second the second, and so on. Two collections of different lengths, or in a different order, is the single most common mistake here — and it fails quietly, because a token that does not match the form's bindings just drops the prefill.
Worked example
A form welkom-2026 with one data-mapping binding on parameter leadId reading from Lead. You want the
nurture email to carry a link that fills the visitor's details in.
1. Start the Flow
A record-triggered flow on Lead, or a scheduled flow over a set of Leads. In this example the record variable is the Lead being processed.
2. Get the Form record
The action needs the Form's record Id, and you should not hardcode one — it differs per org and per sandbox refresh.
Get Records on Form, filtered Form Key equals welkom-2026, storing the first record. Keep the
fault path: if the form is missing you want to know, not to send a broken link.
3. Build the two collections
Create two Text collection variables — varT_ParamNames and varT_RecordIds.
Then an Assignment element:
| Variable | Operator | Value |
|---|---|---|
varT_ParamNames |
Add | leadId |
varT_RecordIds |
Add | {!$Record.Id} |
For a second binding, add another pair — one Add to each collection, in the same order.
4. Call the action
Action → Build Flux Forms Prefill Link:
- Form Id → the Id from your Get Records
- Parameter Names →
varT_ParamNames - Record Ids →
varT_RecordIds - Valid For (Days) →
14, or blank for no expiry
5. Check it worked
A Decision on the action's Success output. On the failure branch, do something with Error Message — log it, or email yourself. Do not send an email containing a link that was never built.
6. Assemble the full URL
The action returns only the query string, so join it to your site address in a Formula of type Text:
'https://acme.my.site.com/forms' & {!Build_Flux_Forms_Prefill_Link.relativeUrl}
Use the same Site Base URL value your administrator set in CMS Media Settings, with no trailing slash. The result looks like:
https://acme.my.site.com/forms?f=welkom-2026&data=<token>
7. Use it
Put the formula into your email template as a link. The visitor clicks through and the mapped fields are already filled in — locked or editable, per the binding's behavior setting.
What the token does and does not protect
- It is bound to one form. Point it at a different form and the prefill drops.
- It is tamper-proof. Edit a character and the prefill drops.
- It expires, if you set Valid For (Days).
- It fails closed in every one of those cases: the form still loads, just empty. Nothing leaks, nothing errors.
- What it may read is decided by the form's Purpose, not by who opens the link. Fields no Purpose marks readable are never filled, no matter what the token says.
Treat a personalised link like a password. Anyone holding it sees the values it carries. Set Valid For (Days) on anything you send out, and do not paste one into a shared channel or a support ticket.
Troubleshooting
| Symptom | Cause |
|---|---|
| Form loads empty | The token is expired, tampered with, or built for another form. Also check the parameter name matches the data-mapping binding exactly. |
| Some fields fill, others do not | The empty ones are not granted read access by any assigned Purpose. |
| Success is false | Read Error Message. Usually a bad Form Id, or mismatched collection lengths. |
| Link 404s | The Site Base URL is wrong, or the site is not published. See Publish the public forms site. |
| Older links stopped working | Links using ?form=<id>, a raw record Id, or ?<field key>=value were removed. Regenerate them with this action. See Prefill links. |
