Workflows and 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.
Workflows automate operations with documents, CRM objects, files, and list items. The bizproc.* methods start processes from templates, manage active instances, process user tasks, and add custom application actions or automation rules to automation.
A process can start automatically when an event occurs in Bitrix24 or manually at the user's initiative. Through the REST API, it is started using the bizproc.workflow.start method.
For new development, application automation rules are usually preferred. Automation rules are available in CRM automation, workflows, and smart scripts, while application actions are useful for supporting existing integrations in the workflow designer.
Quick navigation: all methods
User documentation:
How to Choose a Section
|
If You Need To |
Open the Section |
|
Start a process, retrieve a list of active processes, or stop execution |
|
|
Add, update, retrieve, or delete a workflow template |
|
|
Retrieve, complete, or delegate a user task |
|
|
Add an external step for CRM automation, workflows, or smart scripts |
|
|
Support an external step that is already used in the workflow designer |
How to Start
- Prepare a workflow template in the Bitrix24 interface or add it using bizproc.workflow.template.add
- Define the document for which the process will run. To start a process, you need
DOCUMENT_ID, for example['crm', 'CCrmDocumentLead', 'LEAD_1'] - Start the process using bizproc.workflow.start, and pass
TEMPLATE_ID,DOCUMENT_ID, and the template input parameters - Monitor active processes using bizproc.workflow.instances
- Process user tasks using the bizproc.task.* method group if the scenario requires approval, acknowledgment, or additional information
Relationship with Other Objects
Workflows are linked to Bitrix24 documents, templates, user tasks, and external application handlers.
Document. A process is started for a specific document: a lead, deal, list item, Drive file, or another supported object. The link is passed in the DOCUMENT_ID parameter of the bizproc.workflow.start method. The document type must match the type for which the template was created.
Workflow Template. A template defines the process logic and the set of input parameters. Templates can be managed using the bizproc.workflow.template.* method group. The template identifier TEMPLATE_ID is used when starting a process and filtering the list of active processes.
Workflow Task. A task appears when a process needs a user action: approval, acknowledgment, or additional data input. Tasks can be retrieved using bizproc.task.list, completed using bizproc.task.complete, and delegated using bizproc.task.delegate.
Application. Application automation rules and actions call the external HANDLER. If the handler must return a result to the process, specify output parameters and the response waiting mode during registration, then pass the values using bizproc.event.send.
What to Consider
- Methods for managing templates, automation rules, and actions are executed by an administrator
- Automation rule and action methods work only in the context of an installed application
- An automation rule or action that waits for a result receives
EVENT_TOKENduring scenario execution. This key is required for the bizproc.event.send method - A started process uses a copy of the template as it was at the start time. Changes to the template do not affect an already active process
Overview of Methods
Scope:
bizprocWho can execute the method: depends on the method
Main Workflow Methods
|
Method |
Description |
|
Starts a workflow |
|
|
Retrieves a list of started workflows |
|
|
Deletes a started workflow along with its data |
|
|
Stops workflow execution |
Workflow Templates
|
Method |
Description |
|
Adds a workflow template from a file |
|
|
Updates a workflow template |
|
|
Retrieves a list of workflow templates |
|
|
Deletes a workflow template |
Workflow Tasks
|
Method |
Description |
|
Retrieves a list of workflow tasks |
|
|
Completes a workflow task |
|
|
Delegates a workflow task |
Application Automation Rules
|
Method |
Description |
|
Registers an application automation rule |
|
|
Updates an application automation rule |
|
|
Retrieves a list of application automation rules |
|
|
Deletes an application automation rule |
|
|
Passes automation rule or action output values to the process |
Application Actions
|
Method |
Description |
|
Adds an application action |
|
|
Updates an application action |
|
|
Retrieves a list of application actions |
|
|
Deletes an application action |
|
|
Writes a message to the workflow log |