Collect Information from Users in Agentforce Operations

How Fields Work

Fields are the building blocks for data collection in your workflows. Create custom fields one time and reuse them across multiple blueprints, or use Agentforce Operations system fields that are available in every workspace. After a user provides a value, you can pass that value to subsequent tasks downstream or use it to drive conditional logic in your blueprint.

Fields support a range of data types so you can collect exactly the information your process requires. Select the field type that matches your data: Text for open-ended responses, dates for scheduling, people fields for assignments, and so on.

To learn about how fields relate to blueprints, workflows, and tasks, see How Blueprints, Workflows, and Tasks Connect in Agentforce Operations.

System Fields

Agentforce Operations includes system fields that are available in every workspace without any setup. System fields capture workflow metadata and information from workflows automatically. You don't create or configure these fields. They're available to share with downstream tasks or use in conditions.

To see the list of system fields, go to the Home page and then click Columns. The list of system fields are in the System information section. To see the field's description, hover over the "i" icon next to the field.

Custom Fields

Create custom fields to collect information specific to your processes. Custom fields support different data types to match what you're collecting. For example, use currency fields to capture pricing or budget amounts, number fields to track quantities or percentages, or signature fields to collect electronic approvals. Select fields collect an option from a list, and data source fields can collect information from external systems like CRM or ERP platforms.

Create fields one time and reuse them across multiple blueprints. Add fields to the Request information section to collect data from assignees. The values flow forward automatically to downstream tasks where you can reference them in other fields, conditions, or AI agent prompts.

For a complete list of available field types and their capabilities, see Field Types in Agentforce Operations. To learn how to create and add fields, see Create Custom Fields in Agentforce Operations.

Using Fields to Split Tasks

Use multi-value fields to split tasks into multiple parallel instances at run time. When you configure a task to split based on a multi-select, people, role, document, or data source field, Agentforce Operations creates a separate task instance for each value in that field. You can process multiple tasks in parallel without manually duplicating the same task for each item.

For example, if an upstream task collects a list of suppliers in a multi-select field, you can split a subsequent review task to create one task per supplier. If you split on a people or role field, each person automatically receives their own task assigned to them. Split tasks work with standard tasks, approval tasks, and even AI agent tasks.

To learn more, see Split a Task into Duplicate Tasks in Agentforce Operations.

Forms

Group related fields into forms to organize data collection and improve the user experience. Forms show fields together in a structured layout, which makes it easier for assignees to understand what information they need to provide and why. Forms can contain any combination of field types.

Use forms when tasks request multiple related data points. For example, collecting customer contact information, gathering order details, or requesting project specifications. To learn more, see Create a Form in the Form Builder in Agentforce Operations.

Field Versioning

When you edit a field, Agentforce Operations creates a new version of the field. Field versions make sure that running workflows continue to use the original field definition while new workflows pick up the updated version. Versioning prevents changes from breaking workflows that are in progress.

Field versions apply to select and multi-select fields when you add, remove, or rename options. Other field types create new versions only when you change fundamental properties like data type or validation rules. To learn more, see Manage Field Versions in Agentforce Operations.

Adding Fields to Tasks

Add or remove individual fields on a task without using a form. Use this approach for simple tasks that request only one or two pieces of information. To learn more, see Add or Remove Task Fields Individually in Agentforce Operations.

To learn more, explore these links.