Remove phone from entity by ID
The Remove phone from entity by ID robot strips the given numbers from the card of a lead, contact or company by its type and ID — from any business-process context in Bitrix24 (Alaio). Numbers are given as a list and matching is smart by default: 8 and +7 count as the same number. It returns a removed flag (Y/N), the number of phones removed and the list of removed values.
The robot removes one or more phones from an arbitrary entity — a lead, contact or company given explicitly by type and ID, even when the business process runs on a different CRM entity (for example a deal's process cleaning the linked contact's phone). The numbers to remove are given as a Multiple field (one per line). The match mode is a parameter: "smart" (default) reduces numbers to a 10-digit core and treats 8, +7 and a no-prefix form as the same number; "digits only" compares all digits without reduction; "exact match" compares the string as-is. Internally the robot reads the entity's phone list and deletes only the matching values by their identifiers — the other phones, as well as email and other contact data, are left untouched. If no number is found, no write happens. Typical cases: drop an outdated number on a linked company while working a deal, remove a blacklisted number from external-system data. It returns a Removed (Y/N) flag, the number of phones removed and the list of removed values — use them in the conditions and notifications of later steps. If the robot runs in the entity's own business process, the Remove phone from current entity robot is handier — no ID needed there.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Entity type | select | yes | contact |
| Entity ID | int | yes | |
| Numbers to remove (one per line) | string | yes | |
| How to match numbers | select | yes | smart |
What does the robot return?
| Parameter | Type |
|---|---|
| Removed (Y/N) | string |
| How many numbers were removed | int |
| Removed numbers | string |
What errors can the robot return?
The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.
- API error
- Error: no numbers to remove were provided
- Error: entity ID is not provided
- Error: choose an entity type — lead, contact or company
- Error: a "current entity" robot must run from a lead, contact or company business process
Scenario: drop a linked contact's phone from a deal process
- In the deal business process add the Remove phone from entity by ID robot
- Choose type Contact, set ID to the deal's contact, list the phone to remove in the numbers
- The robot returns Removed = Y and removed_count = 1 if the number was on the card