# Flow: process data in each task

Create text, number, date and yes/no fields, choose the flows that use them and store individual values in each task.

Source: https://zild.ai/en-US/docs/apps/zild-tasks/updates-flow-campos-personalizados-tarefas

Create text, number, date and yes/no fields, choose the flows that use them and store individual values in each task.

## How to use it

In Zild Flow, open Task custom fields and create a field with a display name, technical name, data type and one or more flows. Then open a task in those flows, fill in the fields and reopen it to verify persistence. Use names representing process data, such as project code, received quantity or expected date.

## Limits and prerequisites

Configuration requires company permissions and at least one existing flow. The technical name must be unique within the company, and the type cannot be changed after creation: create another field for a different type. Fields organize data; they do not by themselves create ERP integrations, approval rules or automatic calculations.

## Validate in your operation

In a test flow, create two records with different values and reopen both to verify that each task keeps its own data. Also check an unassociated flow. For existing tasks, wait for saving to finish and resolve any error before closing the panel.

## Operations examples

- Engineering: a text project code, expected review date and a yes/no review-completed indicator.
- Logistics: a text delivery reference and expected exception-resolution date.
- Inventory: received quantity as a number and batch reference as text, preserving leading zeros.

These are suggested configurations. A checked field records a value; it does not by itself establish formal approval, physical receipt or an update in the source system.

## Creating and editing a field

- Create the flow before configuring its fields.
- Open Task custom fields and select New task field.
- Enter a display name and technical name, up to 100 characters each. The technical name must be unique within the company, including case-only differences.
- Choose Text, Number, Date or Yes / No; associate one or more flows and save.
- Reopen configuration to check the association and active status. To change the type, create a new field and plan data transfer; this screen does not perform automatic conversion.

## Task saving and verification

For existing tasks, editing fields triggers saving when leaving the field or changing its selection, depending on the control. Wait for completion and reopen the task to verify. Resolve field-loading errors before saving; if saving fails, values remain in the open form but must not be considered persisted on the server.

Test with two tasks, distinct values and an unassociated flow. Record the expected result, observed result and reviewer. Connect subsequent automation only after validating the required names, types and permissions.

## Availability

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

Documentation reviewed: 2026-10-28.

[Read the announcement](/en-US/blog/flow-campos-personalizados-tarefas)