Skip to content
Flux Forms

Home / Getting started

What is Flux Forms

Branded, multilingual forms that collect straight into Salesforce and trigger what happens next.

Flux Forms lets your team build branded forms, publish them on a public website, collect the answers into Salesforce, and trigger whatever should happen next — creating or updating records, starting a Flow, or publishing a platform event.

describe what the video shows

It runs entirely inside your Salesforce org. There is no separate form tool to log into, no data sitting somewhere else, and no export step: a submitted form becomes a Salesforce record immediately.

What you can build

  • Multi-step forms that show one section per screen with a progress bar, or a single page with all sections stacked.
  • Conditional forms that show, hide, require or disable fields based on the answers given — and that can branch past whole sections, submit early, or dead-end a visitor who does not qualify.
  • Prefilled forms, where a personalised link fills in what you already know about someone, so they confirm rather than retype.
  • Multilingual forms, with a language switcher for visitors and a fallback language for anything left untranslated.
  • Branded forms, styled with reusable themes — colours, fonts, corner radius, logo — that you manage once and apply to many forms.

What makes it different

Two things are worth understanding early, because they shape how the whole product behaves.

Field access is governed, not assumed. A form cannot read or write an arbitrary Salesforce field. An administrator first approves fields through a Purpose, and a form can only touch fields its assigned purposes grant. This is enforced when you save, not just hidden in the interface — so a marketeer cannot widen their own access, by accident or otherwise. See Purposes.

Configuration is versioned. A form's content lives in a Form Config, and one config version is the Active one. Past submissions record which version they were filled in against, so a form you changed last month does not make last month's answers unreadable.

Who does what

Flux Forms expects three roles, and the permission set group you are assigned decides which one you are. Most people are marketeers.

Role Typically does
Marketeer Builds forms: sections, fields, logic, branding, translations, and publishing.
Administrator Approves which fields and flows forms may use, and does the one-time org setup.
Analyst Reads submissions and errors for analysis. Changes nothing.

Next: Getting access.

Last updated: 2026-09-10