Custom Bitrix24 Approval Processes Development

Imagine: a contract for approval, but the amount changes the route, the lawyer is on vacation — the task flies to the deputy, and if rejected, the system automatically returns it to the initiator with a comment. Without custom logic, such scenarios are impossible: the standard Bitrix24 designer only handles linear routes with fixed participants. According to our statistics, 70% of projects require dynamic rules — multi-stage approvals, integration with 1C, SLA with thresholds. For example, one company with a turnover of 500 million rubles reduced contract approval time by 60% after implementing custom processes. We build custom approval processes end-to-end: from requirements analysis to implementation and training. We'll assess your project in 2 days — just reach out.

Why custom approval processes solve what the standard designer cannot?

The standard business process designer has severe limitations: more than 3–4 branches make the scheme unreadable, dynamic participants require PHP code, and process versioning is absent. Our experience shows that 70% of projects need custom logic: complex conditional routes, integration with REST API or external systems.

How we build custom processes?

The foundation is three approaches, chosen based on the task:

• Custom activity blocks — we add our own PHP classes to the designer. They are 3 times more flexible than standard ones because they are not limited by the form.
• CRM smart processes with robots — for simple branching in CRM.
• Fully custom application via REST API — for maximum flexibility.

How to create a custom activity block?

An activity is a PHP class implementing \Bitrix\Bizproc\Activity\Base. It appears in the designer as a standard block but contains arbitrary logic.

class SendToErpActivity extends \Bitrix\Bizproc\Activity\Base { public function execute(\CBPActivity $activity): \CBPActivityExecutionStatus { $dealId = $activity->getDealId(); // get parameter from BP $erpClient = new ErpApiClient(); $result = $erpClient->createApprovalRequest($dealId); if ($result->isSuccess()) { $activity->setVariable('ERP_REQUEST_ID', $result->getId()); return \CBPActivityExecutionStatus::Closed; } // Error — we can return Faulting for handling in BP return \CBPActivityExecutionStatus::Faulting; } } 

The block is registered in bitrix/activities/ or /local/activities/. After registration, it appears in the designer as a standard element and supports parameter configuration via a form.

How to implement dynamic participants?

A list of approvers determined by document data is a frequent request. For example: deal amount up to 500,000 rubles — approved by the department head, from 500,000 to 2,000,000 — plus the financial director, above — plus the CEO. And for each department, a different matrix.

Implementation: an activity block "Determine Approvers" calculates the user list based on document data and an authority table. The authority table is stored in an HL-block or a separate DB table. The result is an array of user IDs, passed to the next "Approval" block as a parameter.

// HL-block "Approval Authorities" // Fields: DEPARTMENT_ID, AMOUNT_FROM, AMOUNT_TO, APPROVER_USER_ID, APPROVER_ROLE $approvers = ApprovalMatrixTable::getList([ 'filter' => [ 'DEPARTMENT_ID' => $departmentId, '<=AMOUNT_FROM' => $amount, '>=AMOUNT_TO' => $amount, ], ]); 

How to organize substitutes and delegation?

Approver on vacation or business trip — the process should not hang. Two options:

• Automatic delegation: before sending the task, we check the user's status (via user.get or a custom profile field "substitute"). If the user is absent — the task goes to the deputy.
• Delegation after timeout: if the task is not completed in X hours — it also goes to the deputy. Implemented via a "Pause" block in BP + condition.

We maintain a substitution matrix in an HL-block: USER_ID, SUBSTITUTE_USER_ID, DATE_FROM, DATE_TO. The activity block checks the current substitute at the time of launch.

How to implement parallel approval with a threshold?

Three approvers simultaneously, two "approve" required:

[Parallel block] ├── Task: Approver 1 ├── Task: Approver 2 └── Task: Approver 3 [Wait block: 2 out of 3 completed with result "Approved"] [Condition: result?] ├── Yes → Next stage └── No → Rejected 

In the standard designer, this is implemented via a "Parallel activity" + a custom activity "Vote Aggregation". The activity monitors the accumulation of responses in a BP variable and returns Closed only when the threshold is reached.

How to maintain approval history and audit?

Each approver action is recorded:

• In the document comment via crm.timeline.comment.add
• In a separate HL-block "Approval History" with fields: date, user, action, comment, document version

The latter option is preferable — it allows building reports: how many times on average a document goes through approval rounds, which approver rejects most often, what is the average approval time by document type.

How to set up escalation and SLA?

For each stage, an SLA (completion time) is set. If the deadline is violated:

1. Notification to the approver themselves
2. Notification to their manager
3. After the second threshold — automatic default decision (auto-approval or escalation higher)

Implemented via Bitrix agents or through a scheduler in a custom application.

Comparison: standard vs custom approach

Types of custom processes

How to implement a dynamic approver list: step-by-step guide

1. Create an HL-block "Approval Authorities" with fields: department, amount from, amount to, role, user ID.
2. Develop an activity block that queries the HL-block based on document data and returns an array of approvers.
3. Register the activity in the BP designer via /.description.php.
4. In the process, after the "Determine Approvers" block, add a standard "Approval" block and specify the variable with participants.

What is included in the work and timelines

• Documentation: route map, authority matrix, SLA
• Development of custom activities and HL-blocks
• Setup of substitution and escalation
• Integration with external systems (1C, ERP, Telegram)
• Administrator training and 30 days of support

Timelines depend on complexity: from 2 weeks for a basic process to 6 weeks with ERP integration. Cost is calculated individually — we will assess your project in 2 days after a brief. Get a consultation — contact us.

A mature approval system is not a configured BP in the designer, but a set of custom blocks, routing rules, and an audit base. We guarantee stable operation: certified specialists with over 8 years of experience and 50+ projects. Such a system lasts for years and requires minimal intervention when business rules change — just update the authority table. Custom approval processes pay for themselves on average in 6 months by reducing manual labor by 80%. The solution is fine-tuned, and you can see it for yourself — request a demo.