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, specifically enabling interaction with its CRM and business process automation features. The "Get Workflows" operation under the "Workflow" resource allows users to retrieve workflow definitions or instances from Bitrix24's business process module.
Typical use cases include:
- Automating retrieval of business process workflows for monitoring or reporting.
- Integrating Bitrix24 workflows into larger automation pipelines.
- Fetching workflow data to trigger conditional logic in n8n based on workflow states or properties.
For example, a user might configure this node to fetch all active workflows related to a sales process and then use that data to update external systems or notify team members.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key. |
| Return All | Whether to return all available workflows or limit the number of results fetched. |
| Max Pages to Load | When not returning all, limits how many pages of results to fetch (each page contains up to 50 items). |
| Options | Additional parameters to customize the request: |
| - Filter | JSON object specifying filter criteria to narrow down workflows returned. |
| - Order | JSON object defining sort order of the results. |
| - Start | Number indicating the starting record number for selection (pagination offset). |
| - Access Token | Optional access token string for authentication override. |
Output
The node outputs an array of workflow objects in the json field of each item. Each object represents a workflow retrieved from Bitrix24, containing details such as workflow ID, name, status, and other metadata as provided by the Bitrix24 API.
If multiple workflows are returned, they will be output as separate items in the main output array.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs appropriate credentials configured in n8n for the chosen authentication method.
- Relies on Bitrix24 API endpoints for business process workflows.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens. OAuth2 requires proper token setup; webhook URLs must be correct and active; API keys must have sufficient permissions.
- Empty results: Check filter criteria and pagination settings. If filters are too restrictive or start index is beyond available records, no workflows may be returned.
- API rate limits or timeouts: Large requests (e.g., returnAll=true) may hit API limits. Use maxPages to limit data volume.
- Malformed JSON in filter/order: The filter and order options expect valid JSON strings. Invalid JSON will cause errors.
- Continue On Fail: If enabled, errors during execution will output error details instead of stopping the workflow.