Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The node integrates with the Bitrix24 platform, specifically allowing users to interact with various Bitrix24 resources such as CRM entities and business processes. For the Task resource with the Pause operation, it enables pausing or halting a task within Bitrix24. This can be useful in automation workflows where tasks need to be temporarily suspended based on certain conditions or triggers.
Practical examples include:
- Pausing a task when waiting for external approval.
- Temporarily halting a task due to missing information or dependencies.
- Automating task management by programmatically controlling task states.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| Options | Collection of optional parameters to customize the request: |
| - Filter | JSON object specifying filter criteria to narrow down tasks. |
| - Order | JSON object defining sorting order of results. |
| - Select | JSON array listing specific fields to retrieve. |
| - Group | JSON object specifying grouping criteria. |
| - Custom Parameters | JSON object for any additional parameters supported by Bitrix24 API. |
| - Access Token | String token used for authentication if applicable. |
Output
The node outputs an array of items, each containing a json property with the response data from Bitrix24 related to the paused task(s). The exact structure depends on the Bitrix24 API response but generally includes task details and status updates.
If an error occurs 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.
No binary data output is indicated.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 API endpoints internally to perform operations.
- No additional external services beyond Bitrix24 are required.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrectly formatted JSON in options like filter, order, select, group, or custom parameters causing API call failures.
- Network connectivity problems preventing access to Bitrix24 API.
Error messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical errors include authentication failures, invalid parameters, or resource not found.
Resolutions:
- Verify and refresh authentication credentials.
- Validate JSON syntax in all input properties.
- Check network connectivity and Bitrix24 service status.