Configure the Start action (user-initiated)

Configure the Start action so employees can begin an agentic workflow from the AI assistant.

The Start action defines:

• How the workflow begins.
• What information is available when a run starts.
• How the assistant recognizes when to start the workflow.

For user-initiated workflows, publishing creates a managed start tool. The assistant can start the workflow only after that tool is attached to the assistant. See Publish a workflow and attach the start tool.

Before you begin

Make sure you have:

• Created a workflow in the designer. See Create a workflow.
• The Experience Designer or Tenant administrator role.
• A clear description of when employees should start this process.

When to use a user-initiated Start

Use User-initiated when an employee asks the AI assistant to complete a task, such as:

• Request vacation or sick leave.
• Update personal information.
• Submit a job or position request.
• Replace equipment.

Use an Event-based Start instead when an external system should start the workflow automatically, such as for a new-hire event. Event-based configuration is covered separately.

Configure a user-initiated Start action

1. Open the workflow in the workflow designer.
2. Select the Start action on the canvas.
3. Set Trigger to User-initiated.

4. Configure how the assistant identifies the workflow.

   Field	Purpose	Example
   Tool Title	Short name the assistant and admins use for the start tool.	Request time off
   Tool Description	Explains when the assistant should start this workflow.	Start when the employee wants to request paid time off, vacation, or sick leave.
   Agent Activity Text	Message employees see while the workflow is starting.	Starting your time off request…

Changes save automatically.

Write a clear Tool Description

The Tool Description helps the assistant decide whether this workflow matches the employee's request.

Good descriptions:

• State the employee intent in plain language.
• Include common phrases employees might use.
• Stay specific enough to avoid starting the wrong workflow.

Avoid vague descriptions such as HR request or Help the employee.

Configure Start inputs

Start inputs are the data available at the beginning of each workflow run.

Keep Start inputs minimal when a later Agent action will collect details from the employee. Often, the Start action only needs identity information from user context.

For example:

Add additional Start inputs only when the value is already known when the workflow starts, and later actions need it immediately.

Optional: Configure workflow steps

Workflow steps are optional progress milestones employees can see while the workflow runs. They aren't the same as every action on the canvas.

1. In the Start action, under Workflow Steps, select Use steps.
2. Set the First step label, for example Gather details.
3. Create later milestones when you configure each action's Workflow Step setting.

Example employee-facing progress:

1. Gather details
2. Submit request
3. Complete

What to do next

• Add an Agent action to collect information or guide the employee.
• Add a Run Tool action when the workflow should call a system directly.
• Publish the workflow and attach the start tool.
• Test the workflow.

Related articles

• Build your first workflow