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, enabling automation of various tasks such as managing CRM entities, workflows, and business processes. Specifically, for the Workflow resource and Complete Task operation, this node facilitates completing a specified task within a Bitrix24 business process workflow.
This is useful in scenarios where you want to automate the progression of business workflows by programmatically marking tasks as complete based on external triggers or data changes. For example, after a customer support ticket is resolved in another system, you could use this node to automatically complete the corresponding task in Bitrix24's workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Task ID | The unique identifier of the task to be completed within the workflow. |
| Parameters | JSON object containing additional parameters for the workflow completion. |
Output
- The node outputs an array of items, each containing a
jsonproperty. - The
jsonoutput typically includes the response from Bitrix24 after attempting to complete the task. - If an error occurs and "Continue On Fail" is enabled, the output will include an
errorfield with the error message, theresourcename, and a timestamp. - The node does not explicitly handle binary data output.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API key authentication.
- The node depends on Bitrix24 API endpoints to perform operations.
- Requires proper configuration of credentials in n8n for the chosen authentication method.
Troubleshooting
- Common Issues:
- Invalid or expired authentication credentials can cause failures.
- Incorrect Task ID may result in errors indicating the task was not found.
- Malformed JSON in the Parameters property can cause request failures.
- Error Messages:
- Errors returned from Bitrix24 API are surfaced in the node output if "Continue On Fail" is enabled.
- Common error messages might include authentication failures, permission denied, or invalid task identifiers.
- Resolutions:
- Verify that the authentication credentials are valid and have sufficient permissions.
- Double-check the Task ID value corresponds to an existing task.
- Ensure the Parameters JSON is correctly formatted.