---
schema_version: "1"
id: e74e9f1d9026244907941fd76b3513d37fd9fec1f367c0177288e3540348b594
title: Autogenerate Workflow Names with Merge Fields in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_workflow_naming.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_workflow_naming.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 186aac3dfaf8e295e8ad0e1ba467f6a43ad45bfa1a38dabfcdbf2f3dbd4a0204
description: Create a naming convention for workflows so each workflow started from a blueprint gets a consistent, descriptive name based on field values in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# Autogenerate Workflow Names with Merge Fields in Agentforce Operations

Create a naming convention for workflows so each workflow started from a blueprint gets a consistent, descriptive name based on field values in Agentforce Operations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d14924e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d14924e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">To create a blueprint from scratch, using AI, or by importing a .rex file in
              Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">Admin role or Creator role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">
              <p style="margin-bottom:0;">To create a blueprint by importing a .docx file in Agentforce Operations:</p>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">To publish a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">Admin role or Publisher role with View access for the blueprint</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d14924e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

          </tr>
        </tbody>
      </table>

Autogenerated workflow names help you quickly identify and organize workflows without relying on manual naming. When you add merge fields to the name, Agentforce Operations replaces each field with the workflow's value for that field. For example, a name template like {Region} - {Supplier} - {Quarter} creates workflow names like EMEA - Acme Corp - Q2.

You can only set up autogenerated workflow names on draft blueprints. To change autogenerate settings after publishing, create a new blueprint version.

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the blueprint, click the **About** tab.
3. Click **Edit blueprint details**.
4. Select **Autogenerate workflow name**.
5. Enter the name template, adding fields where you want them to appear.
    1. To add a field, click **Add fields**.
    2. Search for and select the field you want to include.
6. Check the preview to make sure that the name looks right.
7. Enter a version note that describes the change, such as Updated autogenerated name.
8. Click **Save changes**.
    
    New workflows started from this blueprint use the autogenerated name based on the fields you selected.