Check if a field is filled
The Check if a Field is Filled robot checks whether a field of a Bitrix24 (Alaio) CRM entity — a deal, contact, company or lead — has a value. The inputs are the entity type, its ID and the field code. It returns an is_filled flag with the value Y if the field is non-empty, otherwise N, plus the current field value. Use it for a business process conditional branch.
The robot opens the CRM entity by type and ID, reads the specified field and determines whether it is filled. The inputs are: the entity type (deal, contact, company or lead), the entity ID and the field code — this can be a standard or a custom field. The outputs are: is_filled — a flag of Y if the field is non-empty, otherwise N (an empty string and the value "0" count as not filled), and value — the current field value; for multiple fields the values are joined with a comma. Use it to make sure before a deal stage change that the tax ID or the responsible person is filled, to stop a card without a required field from moving forward, or to route the process down the right branch depending on whether the data is present. If the parameters are invalid or the entity is not found, the robot returns is_filled N and an empty value. The is_filled flag is convenient to compare in the condition of the next step of the business process.
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 | string | yes |
What does the robot return?
| Parameter | Type |
|---|---|
| Field is filled (Y/N) | string |
| Current field value | string |
Scenario: check that a required field is filled
- A deal enters the Invoicing stage
- The robot checks whether the counterparty tax ID field is filled
- On is_filled = Y the process moves on, on N it returns the deal and creates a task to fill the field
Related robots
Related articles
- Bitrix24 automation rule did not run: how to find out why
- Deal fields in Bitrix24: adding custom fields, organizing the card, and automating input
- Required fields in Bitrix24: per-stage setup, bypass routes, and enforcement
- Vacation management in Bitrix24: status, absence chart, and approval workflow
- Approval workflows in Bitrix24: routes, approval sheet and deadlines
- CRM fields in Bitrix24: custom, required, multiple — and automation
- Robots not working in Bitrix24: step-by-step diagnostics and the log
- Data cleaning in Bitrix24 CRM: names, phones, emails and typos
- Task fields in Bitrix24: system, custom and automation
- Document templates in Bitrix24: creation, fields, and the amount in words
- Document approval in Bitrix24: routes, approval sheet, and deadlines
- Triggers in Bitrix24: what they are, how they differ from robots, and why they don't fire
- The "if — then" condition in Bitrix24 robots: complex checks without code
- Business process tasks in Bitrix24: where to find them and how to work with them