Required Fields for Sales Pipelines
Maintaining data integrity is crucial for any sales process. To help your team follow internal regulations and capture critical information at the right moment, Flowlu allows you to configure mandatory fields for specific sales pipelines and individual stages. This ensures that an opportunity cannot progress until the necessary data is provided.
Note: The functionality for stage-specific required fields is available only on premium Flowlu subscription plans (except for legacy Team plan).
Configuring Required Fields
To set up these rules, navigate to the CRM module settings via the side menu or click the gear icon in the top right corner of the CRM module and navigate to the Required fields tab.
To enable a requirement, select any system or custom field from the list.
Important: For technical reasons, you cannot set requirements for Formula fields, Yes/No fields, or Drop-down fields.
In the right-hand sidebar, enable the "Required at the pipeline stage" checkbox. You can then use the interactive menu to select the specific pipelines and stages where this data is mandatory.
After that, the settings can be saved. Information about which Pipelines and in which stages the field is required will also be displayed in the list.
How the Validation Works
Depending on where you set the requirement, the system responds in different ways to ensure your database remains clean.
Requirements on the First Stage
If a field is mandatory for the very first stage of a Pipeline, Flowlu will prevent you from saving a new record if that data is missing. The system will immediately notify you of the specific empty fields.
Important: If the "Opportunity Amount" is mandatory and you have "Apply the automated calculation of the opportunity’s amount" enabled, the Quick Add button on the Kanban board will be disabled to ensure all product data is entered via the full form.
Regarding automated creation, please note that when an opportunity is generated via Web Forms, Telephony, Email, CSV Import, Automation, and API the required field rules are temporarily ignored. This ensures that new leads are always captured. However, these requirements will immediately trigger as soon as a manager tries to move that opportunity to a new stage within the UI.
Requirements on Later Stages
If mandatory fields are set for subsequent stages, you can manage the opportunity normally on earlier steps. However, as soon as you attempt to drag an opportunity card to a mandatory stage, a pop-up window will appear. This allows the user to fill in the missing information instantly without leaving the Kanban board.
Field completion requirements are also checked when using automated actions of the “Move” and “Field Update” types, as well as when creating/modifying opportunities through the API.
Bypassing and "The Bridge Effect"
It is important to note that if a required field is only set for one middle stage, a user could move an opportunity directly from stage 1 to stage 3, effectively bypassing the requirement. To prevent this, we recommend making the field mandatory for all subsequent stages in that Pipeline.
Bulk Editing and Automation
The system also enforces validation during mass actions. If you select multiple opportunities to move them to a new stage, Flowlu will check each one for mandatory data.
If the system detects opportunities with unfilled required fields, it will notify you about this and show the number of opportunities successfully moved to another stage.
