Whitelist flows
Which flows a form may invoke on submit, including on-demand and packaged flows.
For Salesforce administrators.
Each purpose has a Flows section listing the flows a form using that purpose may invoke from a submission action.
Adding one
- Click Add Flow. The picker opens on a list of active autolaunched flows. Type in Search flows to match on flow label or API name, then pick one. Orgs can hold far more flows than one list can show, so the picker returns a page at a time — when it says "More flows match than are shown", keep typing to narrow it.
- The tool automatically reads the flow's input and output variables and shows them for review.
- Click Whitelist Flow to save. The variable contract is captured with the flow, which is what lets the form builder map inputs and outputs by name.
Maintaining them
- Refresh re-reads a flow's variables and its trigger type, in one go. Use it after the flow changes — a stale variable contract is a common cause of a failed submit action.
- The trash icon removes the flow from the whitelist.
Which flows can be whitelisted
Only autolaunched flows — flows with no trigger. Record-triggered, scheduled and platform-event flows are hidden from the picker, because they expect a trigger context and the submit engine cannot start them at all.
Always whitelist from this list rather than typing a name by hand, so the whitelist and the form's Invoke flow action refer to the same name.
On-demand flows
A flow created with the "no trigger, invoked on demand" start cannot be started by Flux Forms directly — Salesforce does not allow it. Flux Forms detects these automatically and runs them through an Apex class in your own org instead.
Whitelist one exactly as you would any other flow. The routing is automatic; there is nothing different to do here.
What it does need is a one-time setup: an Apex handler registered in Apex Handler Settings, and Flow Access for the Automated Process user on that flow. Until that is done:
- the picker tells you so when you select an on-demand flow — you can still whitelist it;
- the flow list flags those rows with Needs Apex handler, so a long whitelist shows exactly which entries cannot run yet;
- the flag clears on its own once a handler is registered;
- at submit time the action fails with a message naming the Setup screen.
The Form Builder stays quiet about this on purpose. It is a configuration job, and only a configuration admin can see or fix it — a warning aimed at a marketeer would be noise.
The two inputs you did not declare
On-demand flows also receive two inputs from Salesforce itself, emailAddress and
individualId, which the flow does not list among its own variables. Flux Forms adds them to the
captured contract automatically, so they appear in the review step with a note explaining where they came
from, and can be mapped from form values in the Invoke flow action.
If the flow happens to define a variable of its own by one of those names, that definition is kept as-is. Nothing to configure either way.
Flows from installed packages
These work too. The picker shows them with their package prefix (acme__Send_Welcome), and Flux
Forms keeps that prefix with the flow so it starts the right one. Just pick it from the list.
A flow whitelisted before version 0.8.0 has no prefix recorded, so Flux Forms treats it as living in your own org. That is correct for your own flows and they need nothing. For a flow from an installed package, remove it and add it again from the picker so the prefix is captured.
What the marketeer sees
Once a flow is whitelisted and the purpose is assigned to a form, the Invoke flow action offers that flow in a dropdown, with its own variables in the inputs and outputs pickers.
If no flow is whitelisted for a form, the flow field and its pickers are hidden entirely, with a note asking for a flow to be whitelisted first. Save also refuses a form that invokes a flow its purposes do not grant.
Apex, not just flows
A purpose can approve Apex classes the same way. See Approve Apex handlers.
