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 Workflow resource with the Get Workflow operation, it retrieves detailed information about a particular workflow by its ID.
Common scenarios where this node is beneficial include:
- Automating retrieval of workflow definitions or statuses within Bitrix24.
- Integrating Bitrix24 workflows into larger automation pipelines.
- Monitoring or auditing workflows programmatically.
For example, a user might configure this node to fetch a workflow's details by providing its ID, then use that data downstream to trigger notifications or update other systems based on the workflow state.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Workflow ID | The unique identifier of the workflow to retrieve. This is a required string input. |
Output
The node outputs an array of items, each containing a json object with the retrieved workflow data from Bitrix24. The structure of the JSON depends on the Bitrix24 API response for the workflow details but typically includes properties describing the workflow configuration, status, and metadata.
If an error occurs during execution and "Continue On Fail" is enabled, 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 output binary data.
Dependencies
Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended)
- Webhook URL
- API key authentication
The node relies on Bitrix24 API endpoints to fetch workflow data.
Proper credentials must be configured in n8n corresponding to the chosen authentication method.
Troubleshooting
Common issues:
- Invalid or missing Workflow ID: The node requires a valid workflow ID; ensure this is correctly provided.
- Authentication failures: Verify that the selected authentication method is properly configured and credentials are valid.
- API rate limits or connectivity issues with Bitrix24 can cause errors.
Error messages:
- Errors thrown by the Bitrix24 API will be surfaced in the nodeβs error output if "Continue On Fail" is enabled.
- Typical error messages may include authentication errors, invalid workflow ID, or network timeouts.
Resolution tips:
- Double-check the workflow ID for correctness.
- Confirm that the API credentials or webhook URL are active and have sufficient permissions.
- Enable "Continue On Fail" to handle errors gracefully in workflows.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Workflows Overview
- n8n documentation on OAuth2 Credentials and Webhook Usage