Configure target fields

Learn how to configure target fields inside AI Actions and collect structured customer information during automated workflows.

Target fields define the information your AI Action should collect from users during conversations.

These fields are useful for:

• lead collection

• support workflows

• booking requests

• customer onboarding

• webhook submissions

Open the Target Fields section

To configure target fields:

1. Open your AI Agent workspace

2. Go to Automations

3. Open AI Actions

4. Create or edit an AI Action

5. Open the Target Fields section

Inside this section, you can configure the fields used during the automation flow.

Add a target field

To create a field:

1. Click Add Field

2. Enter the field details

3. Configure the field behavior

4. Save the field

Each field represents a value the AI should collect from the customer.

Configure field details

Each target field includes configurable settings such as:

• field name

• field description

• field type

• validation behavior

These settings help the AI understand what information should be collected.

Use validation settings

Target fields support validation options visible inside the builder.

Available validation examples shown in the interface include:

• Email

• Phone Number

• Number

Validation helps ensure customer inputs follow the expected format.

Configure required fields

Fields can also be marked as required.

Required fields help ensure important information is collected before the workflow continues.

This is useful for:

• lead qualification

• support escalation

• booking workflows

Use field descriptions carefully

Field descriptions help guide AI behavior during information collection.

Clear descriptions usually improve:

• response quality

• collection accuracy

• workflow consistency

Short and direct descriptions usually work best.

Use target fields with AI Actions

Target fields work together with:

• AI Actions

• Guided Flows

• webhooks

• conversation automations

Collected information can later be passed into workflows or external systems.

Test your field collection flow

Before enabling the workflow publicly:

1. Start a test conversation

2. Submit sample customer inputs

3. Verify validation behavior

4. Confirm fields are collected correctly

Testing helps prevent collection and formatting issues.

Best practices for target fields

For better automation workflows:

• collect only necessary information

• use clear field names

• validate important fields

• avoid overly long forms

Shorter collection flows usually create better customer completion rates.

Next steps

• Connect automations to webhooks

• Create an AI Action

• Create a Guided Flow