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 Bitrix24, a CRM and business platform, to create tasks within the Bitrix24 environment. Specifically, the "Task - Create" operation allows users to programmatically add new tasks by specifying various task details such as title, description, responsible user, deadlines, priority, and status.
Common scenarios where this node is beneficial include automating task creation based on external triggers (e.g., form submissions, emails, or other workflow events), integrating Bitrix24 task management into broader automation pipelines, and ensuring consistent task data entry without manual intervention.
Practical examples:
- Automatically creating follow-up tasks when a new lead is added.
- Generating tasks for team members based on project milestones.
- Creating reminders or action items triggered by external systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| Fields | Collection of task fields to set when creating the task: - Title: Title of the task. - Description: Detailed description. - Responsible User ID: User assigned responsibility. - Deadline: Task deadline. - Priority: Task priority; options are Low (0), Normal (1), High (2). - Status: Current status; options include New, Pending, In Progress, Supposedly Completed, Completed, Deferred, Declined. - Group ID: Group associated with the task. - Created By: User who created the task. - Start Date: Planned start date. - End Date: Planned end date. |
| Options | Additional optional parameters in JSON format: - Filter: Filter criteria. - Order: Sort order. - Select: Fields to select. - Group: Grouping criteria. - Custom Parameters: Any extra parameters to customize the request. |
Output
The node outputs an array of items, each containing a json object representing the created task's data as returned by the Bitrix24 API. This typically includes the task ID, status, timestamps, and all fields provided or generated by Bitrix24 upon creation.
If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs 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 access to a Bitrix24 account with appropriate permissions to create tasks.
- Supports three authentication methods: OAuth2, Webhook URL, or API Key. The user must configure one of these credentials in n8n before using the node.
- Relies on Bitrix24 REST API endpoints to perform operations.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or webhook URLs. OAuth2 tokens may expire and require refreshing.
- Invalid field values: Providing incorrect or malformed values for required fields (e.g., invalid user IDs, dates) can cause API errors. Verify field formats and existence of referenced entities.
- API rate limits: Bitrix24 may impose rate limits; excessive requests might result in temporary failures.
- Error messages: If the node throws an error, the message usually contains the API response or a descriptive message. Enabling "Continue On Fail" allows workflows to handle errors gracefully.
- Missing required fields: Some fields like "Title" or "Responsible User ID" might be mandatory depending on Bitrix24 settings; omitting them can cause failure.