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 perform various operations on its resources. Specifically, the "Lists" resource with the "Add Element" operation allows users to add new elements (items) to a specified list within Bitrix24.
Common scenarios for this node include automating data entry into Bitrix24 lists, such as adding new contacts, tasks, or custom records based on external triggers or workflows. For example, when a new lead is captured via a web form, this node can automatically add that lead as an element in a Bitrix24 list.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| List ID | The identifier of the Bitrix24 list where the element will be added. |
| Fields | Collection of fields to set on the new element. Each field has: - Field Name: the name/key of the field - Field Value: the value to assign |
| Options | Additional optional parameters: - Access Token: override the default token with a specific one - Filter: JSON object to filter data (not typically used for adding) - Order: JSON object specifying sort order (not typically used for adding) - Select: Comma-separated list of fields to select (not typically used for adding) |
Output
The node outputs an array of items, each containing a json property representing the response from Bitrix24 after adding the element. This typically includes details about the newly created element, such as its ID and any other returned metadata.
If the node encounters an error and is configured to continue on failure, 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.
- Needs authentication credentials configured in n8n, supporting OAuth2, webhook URL, or API key methods.
- Uses Bitrix24 API endpoints internally to perform operations.
- No additional external dependencies beyond standard HTTP requests to Bitrix24.
Troubleshooting
- Authentication errors: Ensure the selected authentication method is correctly configured with valid credentials or tokens.
- Invalid List ID: Verify that the List ID corresponds to an existing list in Bitrix24 and that the authenticated user has permission to add elements.
- Field errors: Make sure the field names and values conform to the expected schema of the target list; invalid or missing required fields may cause API errors.
- API rate limits or connectivity issues: Network problems or Bitrix24 API limits might cause failures; retry or check API status.
- Error messages: If the node throws an error, it usually contains the message from Bitrix24 API. Use this message to diagnose issues like permission denied, invalid parameters, or malformed requests.