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 platform, allowing users to interact with various Bitrix24 resources such as CRM entities and business processes. Specifically, for the Status resource with the Get Status operation, the node retrieves detailed information about a particular status by its ID.
Common scenarios where this node is beneficial include:
- Fetching the current state or metadata of a status in Bitrix24 workflows or CRM pipelines.
- Automating status checks within business automation workflows.
- Integrating Bitrix24 status data into other systems or dashboards.
For example, a user might want to retrieve the details of a deal stage status to trigger further actions based on that status's properties.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Status ID | The unique identifier of the status to retrieve. This is required for the Get Status operation. |
Output
The node outputs JSON data representing the retrieved status object from Bitrix24. The exact structure depends on the Bitrix24 API response but typically includes fields describing the status such as its ID, name, sort order, color, and any other metadata associated with that status.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the status, but this is not applicable for the Get Status operation.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node relies on Bitrix24's REST API endpoints to fetch status information.
- Proper configuration of the authentication method in n8n is necessary to ensure successful API calls.
Troubleshooting
Common Issues:
- Invalid or missing Status ID will cause the API call to fail.
- Incorrect or expired authentication credentials will result in authorization errors.
- Network connectivity issues may prevent communication with Bitrix24 API.
Error Messages:
- Errors returned from Bitrix24 API are surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages include "Unauthorized", "Not Found" (if status ID does not exist), or "Bad Request".
Resolutions:
- Verify the Status ID is correct and exists in Bitrix24.
- Ensure authentication credentials are valid and have sufficient permissions.
- Check network connectivity and proxy/firewall settings if applicable.