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
This node integrates with the Bitrix24 CRM and business platform, allowing users to interact with various Bitrix24 resources. Specifically, for the Status resource with the Get Status Fields operation, it retrieves metadata about status fields available in Bitrix24 entities. This is useful when you want to dynamically fetch and use status-related field information within your workflows, such as for filtering, updating, or displaying status data from Bitrix24.
Common scenarios include:
- Automating CRM processes that depend on status changes.
- Dynamically populating dropdowns or options in subsequent workflow steps based on current status fields.
- Synchronizing status information between Bitrix24 and other systems.
Example: You might use this node to get all possible deal statuses so that you can route deals differently depending on their current status.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of items where each item contains a json object representing the retrieved data from Bitrix24. For the "Get Status Fields" operation, the output JSON typically includes details about the status fields such as field IDs, labels, types, and whether they are required.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with:
error: The error message.resource: The resource name ("Status").timestamp: The ISO timestamp of the error occurrence.
No binary data output is indicated by the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 API endpoints internally to fetch resource-specific data.
- Requires proper configuration of credentials in n8n corresponding to the chosen authentication method.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or permission restrictions on the Bitrix24 account.
- Network connectivity problems preventing API calls.
Error messages:
- Errors thrown during API calls will be surfaced as exceptions unless "Continue On Fail" is enabled.
- If fields fail to load, the node may return an error description in the output indicating the failure reason.
Resolutions:
- Verify and refresh credentials.
- Ensure the Bitrix24 user has sufficient permissions.
- Check network access and proxy settings if applicable.
- Enable "Continue On Fail" to handle errors gracefully in workflows.