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 node integrates with the Bitrix24 platform, specifically allowing users to update a status entity within Bitrix24. This operation is useful for automating workflows where the status of CRM items or other business process elements needs to be programmatically changed based on external triggers or internal logic.
Common scenarios include:
- Automatically updating the status of deals, leads, or tasks after certain conditions are met.
- Synchronizing status changes from external systems into Bitrix24.
- Managing custom statuses in Bitrix24 Smart Processes or CRM entities.
For example, a user could set up an automation that updates the status of a sales lead to "Contacted" once an email campaign is sent, or change the status of a support ticket when a customer responds.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key |
| Status ID | The unique identifier of the status to update |
| Fields | Collection of fields to update on the status: |
| - Name | New name for the status |
| - Sort Order | Numeric value defining the order of the status |
| - Extra | Additional parameters as a JSON object |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 after attempting to update the status. The exact structure depends on the Bitrix24 API response but generally includes confirmation of the updated status fields.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not explicitly output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication token
- Bitrix24 webhook URL
- API key credential
- The node relies on Bitrix24's REST API endpoints to perform operations.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
- Invalid Status ID: If the provided Status ID does not exist or is incorrect, the API call will fail. Verify the ID before running the node.
- Malformed JSON in Extra field: The "Extra" field expects a valid JSON object; invalid JSON syntax will cause errors.
- API rate limits or connectivity issues: Network problems or Bitrix24 API limits may cause failures; check connectivity and retry policies.
- Error messages: When an error occurs, the node returns an error message in the output JSON. Review this message to identify the cause.