Application Automation Rules: Overview of Methods
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Application Automation Rules add a step to Bitrix24 automation that invokes an application handler. This step accepts input parameters, can wait for a response from an external system, and return output values to the workflow.
In the REST API, Application Automation Rules and application actions are similar in model. Each type has separate methods for registration, updating, deletion, and listing. A common execution mechanism is used within the platform.
Automation Rules can be utilized in CRM automation, workflows, and Smart scripts. Therefore, for new development, it is recommended to choose Automation Rules, while application actions should primarily be used to support existing integrations.
Quick navigation: all methods
User documentation:
What Tasks Do Application Automation Rules Solve
- Perform external actions in CRM automation and workflows.
- Return computed data to the process for subsequent steps.
- Restrict availability based on document type and Bitrix24 edition.
- Log messages during the execution of the script.
How Result Waiting Works
If the Automation Rule needs to wait for a response from an external system, specify RETURN_PROPERTIES and USE_SUBSCRIPTION = 'Y' when registering or updating via bizproc.robot.add and bizproc.robot.update.
The script then operates as follows:
- The Automation Rule is triggered in the automation and sends data to the application handler
HANDLER. - The application receives a unique key
EVENT_TOKENand calculates the result. - The application returns values to the process using the method bizproc.event.send.
- If necessary, the application adds a note to the process log via
LOG_MESSAGE.
User Documentation
How to Get Started
- Register the Automation Rule using the method bizproc.robot.add.
- Place the Automation Rule in the desired CRM automation or workflow and start the script.
- Update the Automation Rule settings using the method bizproc.robot.update.
- Check the list of registered Automation Rules via bizproc.robot.list.
- Remove outdated Automation Rules using the method bizproc.robot.delete.
Important Considerations
- The methods for managing Automation Rules bizproc.robot.add, bizproc.robot.update, bizproc.robot.list, bizproc.robot.delete only work in the context of the installed application.
- For bizproc.event.send, a valid
EVENT_TOKENis required; otherwise, the method will return an access error.
Relationships with Other Objects
- CRM Objects. Through
DOCUMENT_TYPEandFILTER, the Automation Rule connects with leads, deals, and other document types where it should be available. - Application Actions. Automation Rules and actions use a common internal mechanism, so it is important to choose a primary path for new scenarios when designing the integration.
Overview of Methods
Scope:
bizprocWho can execute the method: depends on the method
|
Method |
Description |
|
Registers a new Automation Rule |
|
|
Updates the fields of the Automation Rule |
|
|
Retrieves a list of Automation Rules registered by the application |
|
|
Deletes a registered Automation Rule |
|
|
Sends the output values of the Automation Rule or action to the process |