Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform within n8n workflows. Specifically, for the Workflow resource and Start Workflow operation, this node enables starting a predefined workflow template on a specified document in Bitrix24. This is useful for automating business processes such as approvals, notifications, or custom logic triggered by changes in CRM data.
Practical examples include:
- Automatically initiating an approval workflow when a new deal is created.
- Starting a document review process when a contract document is uploaded.
- Triggering a customer onboarding workflow based on lead information.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Template ID | The identifier of the workflow template to start. |
| Document ID | The identifier of the document on which the workflow will be started. |
| Parameters | JSON object containing parameters to pass to the workflow when starting it. |
Output
The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to start the workflow. If an error occurs and "Continue On Fail" is enabled, the output will contain an error message along with the resource name and a timestamp.
No binary data output is indicated.
Dependencies
Requires valid Bitrix24 credentials configured in n8n, supporting one of the following authentication methods:
- OAuth2 token
- Webhook URL
- API key
The node depends on Bitrix24's API endpoints to start workflows and requires network access to Bitrix24 services.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials can cause failures.
- Incorrect Template ID or Document ID will result in errors from Bitrix24 API.
- Malformed JSON in Parameters may cause request rejection.
Error messages:
- Errors thrown by the Bitrix24 API are caught and returned if "Continue On Fail" is enabled; otherwise, they stop execution.
- Typical error messages include authentication failures, missing required fields, or invalid workflow/template identifiers.
Resolution tips:
- Verify that the authentication method and credentials are correctly set up.
- Double-check Template ID and Document ID values.
- Ensure JSON parameters are well-formed and match expected input for the workflow.