Skip to main content
The Account creation screen flow gives sellers a form to review and complete before they create a new Salesforce Account from a Pipeline agent. You can add fields, require information, and show helpful messages using Salesforce Flow Builder. The key change is when the Account is saved: the seller creates it in the flow first, then activates the strategy using that Account. Start with How Account creation works in Pipeline agents to compare this option with the ShiftUp form and understand when the Before Create flow runs.
This guide applies to ShiftUp 3.294.0 and later. The setting is off by default. You need an administrator with ShiftUp Admin and Salesforce’s Manage Flow permission to configure it.

Enable the flow

Configure and check your override in a sandbox before enabling it for your team. If you already use Before Create, review which defaults need to move first.
  1. Open ShiftUp Admin → Advanced → App Settings.
  2. Find the Pipeline Agents & Workspace section.
  3. Turn on Enable Account Creation Flow.
  4. In a Pipeline agent’s Agent results, open an Account choice and select Create new account to see the form.
The Account creation flow setting in ShiftUp App Settings

Enable Account Creation Flow controls the screen flow. The customizable form is a separate setting.

The screenshot shows the setting turned off; enable it when your configuration is ready.
Enable Account Creation Flow takes precedence over Enable customizable Account creation form. The Account form fields list and your Account page layout do not add inputs to this flow. Use Flow Builder for its fields and checks.
While this setting is on, create or choose the target Account and any required parent before activation. Activate and Retry activation remain unavailable while either is missing. Activation applies to checked, eligible rows only; whole-result-set activation is unavailable. The standard flow is called ShiftUp Pipeline Account Create. It shows Account Name, Account Owner, Website, Industry, Phone, Employees, and Billing Address. It also offers the business Account record types the seller can use, when applicable. The owner starts as the seller. ShiftUp fills in available company details when field permissions allow it and Disable account field auto-fill is off. Sellers can review and change those details. Do not expect every field to arrive filled in.
New Account form with the owner, company details, and billing address

The standard screen flow, shown with sample data in a Salesforce test org.

Check seller access

Sellers need permission to create Accounts and access the fields you add. ShiftUp Admin, ShiftUp Manager, ShiftUp Seller, ShiftUp Restricted Seller, and ShiftUp Pipeline Agent Manager include access to the packaged flow and its record type actions. Sellers can run the flow with their seller permission set alone. Creating or editing an override still requires Manage Flow. If you restrict access to your custom override, grant the sellers access to that override through an appropriate permission set. The flow runs as the seller, so Salesforce permissions, validation rules, and duplicate rules still apply. If a seller chooses another owner, Salesforce sharing must still let that seller see the created Account so ShiftUp can link it to the strategy.

Customize the form

A flow override is your organization’s editable version of the packaged flow. Salesforce runs your active override when ShiftUp opens the standard flow.
1

Open the correct flow

In Salesforce Setup, search for Flows, then open ShiftUp Pipeline Account Create.This is the Screen Flow. The similarly named ShiftUp Pipeline Account Before Create has a different purpose, explained below.
2

Save a linked override

Click Save As New Flow. Give it a clear label, such as Custom ShiftUp Pipeline Account Create.The save dialog should say the new flow overrides the packaged flow. Save it and confirm the Override badge in Flow Builder. An unrelated flow with a similar name will not be used automatically.Keep the original flow’s resources, Account creation step, returned Account ID, and error-handling connections. Also keep the Get Person Account Record Types and Set Account Record Type actions and their input and output mappings. They handle the seller’s record type choice, and your override can save and activate with them in place. You will add to these in the next steps.
3

Open the New Account screen

On the flow canvas, select the New Account screen and choose Edit. This is the form the seller sees.

Example: require an Account Number

Suppose your team wants sellers to enter an Account Number of 5–40 characters, such as ACME-001, before creating an Account. This example uses Salesforce’s existing Account Number field, so you do not need to create a custom field to follow along.

1. Add the field to the screen

The Flow Builder screenshots show an example being configured in a scratch org. In your org, make these changes in the linked override created above. In the New Account screen editor, drag a Text component from the Components panel onto the form. Configure it as follows: The label is what sellers see. The API name is how the flow identifies this input; keep it exactly as shown if you use the formula below. Under Advanced, keep Use values from when the user last visited this screen so the seller keeps their answer if a save fails.
Account Number text component with its label, API name, and Require setting

Add a Text component and make Account Number required.

For your own custom field, create it first under Setup → Object Manager → Account → Fields & Relationships → New, or use a field that already exists. Give sellers the required field access. Then add a suitable screen component: Text for a text field, Number for a number, or a Picklist with valid choices for a picklist field.

2. Add a friendly validation message

With the Account Number component selected, expand Validate Input. Paste this formula:
Set the Error Message to:
Enter an account number between 5 and 40 characters, such as ACME-001.
This check ignores spaces at the beginning and end when counting characters. The Require setting handles an empty input. The formula handles an entry that is too short or too long.
Validate Input formula and a plain-language error message for Account Number

A screen validation formula must be true for the seller to continue.

A screen’s Validate Input formula works differently from an Account Validation Rule: the screen formula is true when the entry is valid. An object validation rule is true when Salesforce should block the save. Use a screen check for immediate guidance here; use an Account validation rule when the requirement must also apply outside this flow.
Click Done to return to the flow canvas.

3. Save the answer on the Account

Adding a field to the screen collects an answer. You also need to tell the flow where to save it. Open the existing Apply Seller Values Assignment element. Add this row, leaving its other assignments in place: Use the resource picker to select Account Number on the account record variable, then select the Account_Number screen component as the value.
Apply Seller Values assignment mapping Account_Number to account.AccountNumber

Map the seller's answer to the Account field before Create Account runs.

For a custom field, select that field on account instead. For example, an input called Customer_Code would map to account.Customer_Code__c if that is your field’s API name. The existing Create Account element saves the account record variable. The existing Set Created Account element returns the created Account’s ID to ShiftUp. Keep both steps and the error path that returns the seller to the form if Salesforce rejects the save.

4. Save, check, and activate

Save your override and try it in a sandbox with a seller’s permissions before making it active for your team. Check these examples: When ready, click Activate on the override. Then open Create new account from a Pipeline agent and confirm your added field appears. A standalone preview does not prove that ShiftUp is using the linked override.
Completing Create Account saves a real Salesforce record. Activating the strategy is a separate next step. Cancelling or postponing activation afterward does not undo the Account creation.

What the seller’s flow looks like

For a fictional company, Acme Manufacturing:
  1. The seller reviews a proposed strategy and opens its Account choice.
  2. The seller checks for an existing Account. If none fits, they choose Create new account.
  3. The form opens with the available company details. The seller confirms the owner and record type, then enters ACME-001 in Account Number.
  4. The seller selects Create Account. Your screen checks run, then Salesforce applies its Account rules.
  5. The flow creates the Account and ShiftUp saves it as the strategy’s Account choice.
  6. The seller selects the strategy and clicks Activate. If a new parent Account is also needed, they create or choose that parent first.

If you already use the Before Create flow

ShiftUp Pipeline Account Before Create supplies field values when activation creates a new Account. The new ShiftUp Pipeline Account Create screen flow creates the Account earlier, so it is already an existing Account when activation starts. Your Before Create override does not run for that already-created Account. Add any required defaults or checks to your screen-flow override before turning on the setting. See the Before Create flow guide for that separate setup.

Troubleshooting and turning it off

To return to the packaged screen flow, deactivate your override. To return to creating Accounts during activation, turn off Enable Account Creation Flow in App Settings. Accounts already created keep their saved values.
These resources are already supplied. You do not need to create new ones for the example above.If you need different screens or defaults for a parent Account, accountDraft.accountType is Parent for a supporting parent and Target for the Account used by the strategy. This is separate from Salesforce’s Account Type field. Parent drafts may contain only the proposed name and this role, so collect any other required information on the screen.