> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shiftupai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Account creation works in Pipeline agents

> Understand the two ways to collect Account details, when Salesforce saves the records, and when the Before Create flow runs.

When a seller reviews a strategy in **Agent results**, they choose the Salesforce Account that the strategy will use. They can select an existing Account or choose **Create new account**.

For a new Account, your organization chooses between two experiences:

* **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 **ShiftUp Pipeline Account Before Create** flow is a separate, behind-the-scenes step. It supplies field values when activation creates an Account. It is not a form and does not create the record itself.

> [!NOTE]
>
> 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

| | ShiftUp form | Account creation screen flow |
| - | - | - |
| What completing the form does | Saves the proposed Account details as a **draft**. | Saves a **real Salesforce Account** and links it to the strategy. |
| When the Account is created | When the seller **activates the strategy**. | When the seller selects **Create Account** in the flow, **before activation**. |
| How you add fields | Enable the customizable form and select **Account form fields** in App Settings. | Add screen components and field assignments in a linked **Flow Builder override**. |
| When Salesforce Account validation rules run | When activation tries to save the Account. Required form inputs are checked earlier. | When the flow tries to save the Account. You can also add screen checks before that step. |
| Does the Before Create flow run? | **Yes, for each new Account created by the current activation process.** | **No, for Accounts created by the screen flow.** They already exist at activation. |
| If the seller postpones activation | The details remain a draft; no new Account has been saved by the form. | The Account already exists and remains in Salesforce. |

## 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.

Both versions save draft details. Enabling the customizable version changes the fields sellers can fill in; **it does not change when the Account is created**. The customizable form uses Salesforce field controls, but it is ShiftUp's form, not a copy of your Account page layout.

The sequence is:

1. The seller checks for an existing Account and chooses **Create new account** if needed.
2. The seller completes the form and saves the Account details. ShiftUp keeps them with the proposed strategy as a draft.
3. The seller selects **Activate**. ShiftUp prepares any new Accounts and runs **ShiftUp Pipeline Account Before Create** for each one.
4. 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.

For example, a seller enters **Acme Manufacturing** and its customer classification on Monday, then activates the strategy on Tuesday. **The Account is created on Tuesday.** A Before Create override can supply an additional default, such as an internal category, during that creation.

Follow [Configure and use the ShiftUp Account form](https://docs.shiftupai.com/how-to/customize-account-creation-form.md) to choose the fields, or [Set defaults with the Before Create flow](https://docs.shiftupai.com/customize-accounts-created-by-pipeline-agents.md) to supply values automatically at activation.

## 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:

1. The seller checks for an existing Account and chooses **Create new account** if needed.
2. The seller completes the screen flow and selects **Create Account**.
3. 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.
4. The seller selects **Activate**. The Account already exists, so activation uses it without running **ShiftUp Pipeline Account Before Create** for it.

In the same Monday/Tuesday example, **the Account is created on Monday**, as soon as the seller completes the screen flow. It remains in Salesforce even if the seller never activates the strategy on Tuesday.

While this option is on, a strategy needs an existing target Account and any required parent Account before it can activate. Sellers activate checked, eligible rows; whole-result-set activation is unavailable.

Follow [Set up the Account creation screen flow](https://docs.shiftupai.com/how-to/account-creation-screen-flow.md) for enablement, a field-and-validation example, and screenshots.

## Which setting chooses the form?

Find both settings under **ShiftUp Admin → Advanced → App Settings → Pipeline Agents & Workspace**.

| Enable Account Creation Flow | Enable customizable Account creation form | What sellers get |
| - | - | - |
| **Off** | **Off** | The short ShiftUp form; Account creation happens at activation. |
| **Off** | **On** | The customizable ShiftUp form; Account creation still happens at activation. |
| **On** | Either value | The Account creation screen flow; Account creation happens before activation. |

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.

| Situation | Does Before Create run? |
| - | - |
| A seller saves details in either ShiftUp form | **No.** This saves a draft only. |
| Current Pipeline activation creates a new target Account | **Yes**, before ShiftUp saves that new record. |
| Current Pipeline activation also creates a new parent Account | **Yes**, separately for the new parent. |
| The screen flow creates an Account before activation | **No.** Put the needed defaults and checks in the screen-flow override. |
| Activation uses an Account that already exists, including one created by the screen flow | **No** for that existing Account. |
| A retry reuses an Account that was already created | **No** for the reused Account. |

> [!TIP]
>
> Before switching from the ShiftUp form to the screen flow, review your Before Create override. Move any defaults or checks the new Account still needs into the screen-flow override. They do not carry over automatically.

### 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.

For example, if **Acme Manufacturing** already exists but **Acme — Phoenix Site** is new, only the site needs to be created. The existing parent does not pass through Before Create.

> [accordion] 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.

## Configure the option you need

| Your goal | Guide |
| - | - |
| Let sellers enter more fields while keeping Account creation at activation | [Configure and use the ShiftUp Account form](https://docs.shiftupai.com/how-to/customize-account-creation-form.md) |
| Create Accounts before activation and customize screens or validation messages | [Set up the Account creation screen flow](https://docs.shiftupai.com/how-to/account-creation-screen-flow.md) |
| Supply field defaults when activation creates Accounts | [Set defaults with the Before Create flow](https://docs.shiftupai.com/customize-accounts-created-by-pipeline-agents.md) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.