- The ShiftUp form collects and saves draft details. Activation creates the Account later. You can enable its customizable version to add Account fields.
- The Account creation screen flow collects details and creates the Account immediately when the seller completes it. The seller then activates the strategy using that Account. You customize this experience in Salesforce Flow Builder.
The options described here are available in ShiftUp 3.294.0 and later. The settings apply across your organization, rather than to an individual Pipeline agent.
Compare the two options
Option 1: collect details now, create at activation
Use the ShiftUp form when you want sellers to prepare Account details while reviewing a strategy and leave record creation until activation. There are two versions of this form:- Short form: Name, Website, and Industry.
- Customizable Account creation form: required fields followed by the Account form fields your admin selects. This can include standard fields and eligible custom fields.
- The seller checks for an existing Account and chooses Create new account if needed.
- The seller completes the form and saves the Account details. ShiftUp keeps them with the proposed strategy as a draft.
- The seller selects Activate. ShiftUp prepares any new Accounts and runs ShiftUp Pipeline Account Before Create for each one.
- Salesforce saves the Accounts if its rules pass, and ShiftUp continues creating the strategy. If Account creation fails, the seller or admin must correct the issue before retrying.
Option 2: create the Account before activation
Use the Account creation screen flow when you want sellers to complete your Account creation process and resolve errors before they activate a strategy. The packaged screen flow is called ShiftUp Pipeline Account Create. It includes company details, Account Owner, and a Record Type choice when applicable. Your admin can add fields, required inputs, conditional screens, and validation messages in a linked override. The sequence is:- The seller checks for an existing Account and chooses Create new account if needed.
- The seller completes the screen flow and selects Create Account.
- The flow checks the entries and attempts to save the Account. If Salesforce rejects it, the seller sees the error and can correct the form. On success, ShiftUp links the saved Account to the proposed strategy.
- The seller selects Activate. The Account already exists, so activation uses it without running ShiftUp Pipeline Account Before Create for it.
Which setting chooses the form?
Find both settings under ShiftUp Admin → Advanced → App Settings → Pipeline Agents & Workspace.
Both settings default to off. Enable Account Creation Flow takes precedence when both are on. The Account form fields list configures the customizable ShiftUp form; it does not add fields to the screen flow.
When does Before Create run?
ShiftUp Pipeline Account Before Create has no seller-facing screen. It receives an Account that has not been saved yet, lets your override supply field values, and returns it to ShiftUp to save. For example, it can fill a required classification or apply different defaults for a target Account and its parent.What about parent Accounts?
A strategy for a division or site may also need a parent Account. The creation timing applies to each record:- With the ShiftUp form, activation can create the new target and the new parent. Before Create runs separately for each new Account. An existing parent is reused.
- With the screen flow, create or select the target and any required parent before activation. A new parent uses the same screen flow and is saved immediately. Neither already-created record goes through Before Create at activation.
Older candidates and activations already in progress
Older candidates and activations already in progress
Older candidates that still use a legacy Account creation path may not run Before Create. Check those separately before relying on an override to supply required values.Turning on the screen-flow setting does not change an activation already in progress. That activation can finish using its earlier creation process.

