Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform

Actions290

Overview

The Bitrix24 node integrates with the Bitrix24 CRM and business platform, allowing users to interact programmatically with various Bitrix24 resources. Specifically, the Task - Start operation initiates or starts a task-related process within Bitrix24. This can be useful for automating task creation, management, or triggering workflows based on tasks in Bitrix24.

Common scenarios include:

  • Automatically starting tasks when certain conditions are met in other systems.
  • Integrating task management into broader automation workflows.
  • Filtering and sorting tasks dynamically before starting them.

Example use case:

  • A sales team uses Bitrix24 for task tracking. When a new lead is qualified, an automated workflow triggers this node to start a related task with specific filters and parameters applied.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication.
Options Collection of optional JSON parameters to customize the task start operation:
  Filter JSON object defining criteria to filter which tasks to start.
  Order JSON object specifying the sort order of tasks.
  Select JSON array listing fields to select from the tasks.
  Group JSON object defining grouping criteria for tasks.
  Custom Parameters Additional custom parameters in JSON format to pass to the API call.

Output

The node outputs an array of items where each item contains a json property representing the response from Bitrix24 after attempting to start the task(s). The structure typically includes:

  • Task details as returned by Bitrix24.
  • In case of failure (if "Continue On Fail" is enabled), an error object with:
    • error: Error message string.
    • resource: The resource name ("task").
    • timestamp: ISO timestamp of the error occurrence.

No binary data output is indicated.

Dependencies

  • Requires valid Bitrix24 credentials configured in n8n, supporting one of:
    • OAuth2 authentication (recommended).
    • Webhook URL authentication.
    • API key authentication.
  • Uses Bitrix24 API endpoints internally via a generic resource handler factory.
  • No additional external dependencies beyond Bitrix24 API access.

Troubleshooting

  • Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials. OAuth2 tokens may expire and need refreshing.
  • Invalid JSON in options: The filter, order, select, group, and customParameters fields expect valid JSON. Malformed JSON will cause errors.
  • API rate limits or connectivity issues: Bitrix24 API may throttle requests or be temporarily unavailable.
  • Error messages: If the node throws an error, it will include the Bitrix24 API error message. Enabling "Continue On Fail" allows workflow continuation with error details in output.
  • Missing required parameters: Although not explicitly shown, some Bitrix24 API calls require mandatory fields; ensure all necessary parameters are provided.

Links and References


This summary is based solely on static analysis of the provided source code and input properties definition.

Discussion