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 Field" operation allows users to add custom fields to a specified list within Bitrix24. This is useful for extending the data structure of lists to capture additional information tailored to specific business needs.
Common scenarios include:
- Adding new metadata fields to track custom attributes in project or task lists.
- Extending contact or deal lists with extra details not available by default.
- Dynamically modifying list schemas as business requirements evolve.
For example, a user might add a "Priority" field to a task list to better categorize tasks or add a "Customer Feedback" field to a product list.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| List ID | The identifier of the target list where the new field will be added. |
| Fields | One or more fields to add, each with: - Field Name: The name of the new field. - Field Value: The value or configuration for the field. |
| Options | Additional optional parameters: - Access Token: Override the default credential token. - Filter: JSON filter criteria. - Order: JSON sort order. - Select: Comma-separated list of fields to select. |
Output
The node outputs an array of items corresponding to the result of the add field operation. Each item contains a json object representing the response from Bitrix24 after attempting to add the field(s). This typically includes confirmation of the added field(s) or error details if the operation failed.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message along with the resource name and a timestamp.
No binary data output is indicated.
Dependencies
- Requires valid authentication with Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node relies on Bitrix24's API endpoints to manage lists and fields.
- No additional external services are required beyond Bitrix24 itself.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured and that tokens or keys are valid and have sufficient permissions.
- Invalid List ID: Verify that the provided List ID exists in Bitrix24 and that the authenticated user has access rights.
- Field configuration issues: Make sure the field names and values conform to Bitrix24's expected formats and constraints.
- API rate limits or connectivity problems: Check network connectivity and Bitrix24 API usage limits.
- Error messages in output: If the node returns an error in the output JSON, review the error message for clues and adjust parameters accordingly.
- Enabling "Continue On Fail" can help process multiple items even if some fail, allowing partial success.