Clear a field
The Clear a field robot writes an empty value into a specified field of a CRM entity in Bitrix24 (Alaio) business processes and robots. It takes the entity type (deal, contact, company, lead), the ID and the field code (e.g. UF_CRM_123456 or COMMENTS) and returns a Y/N success flag. It works with both standard and custom fields.
The robot sets an empty value in any field of a deal, contact, company or lead — without editing the card by hand. Provide the entity type (deal / contact / company / lead), its ID and the field code: both system fields (e.g. COMMENTS) and custom fields (UF_CRM_123456) are supported. This is useful when a field value becomes outdated during the process and needs to be reset: for example, clear the loss reason when a deal returns to work, blank a service field before a re-run, or wipe a temporary marker. The robot returns a Y/N flag — check it in the condition of the next step to confirm the clearing succeeded.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Entity type: deal / contact / company / lead | string | yes | |
| Entity ID | int | yes | |
| Field code (e.g. UF_CRM_123456 or COMMENTS) | string | yes |
What does the robot return?
| Parameter | Type |
|---|---|
| Success (Y/N) | string |
Scenario: resetting the loss reason when reviving a deal
- A deal returns from the Lost stage back to work
- The Clear a field robot empties the loss-reason field on that deal
- On a Y flag the process continues with a clean card
Related robots
Related articles
- Deal fields in Bitrix24: adding custom fields, organizing the card, and automating input
- Required fields in Bitrix24: per-stage setup, bypass routes, and enforcement
- CRM fields in Bitrix24: custom, required, multiple — and automation
- Sales funnel report in Bitrix24: why it lies and how to fix it
- Dependent and hidden fields in Bitrix24: how to set them up without a developer