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 the Bitrix24 CRM and business platform, specifically allowing users to add log messages to the timeline of various CRM entities such as Leads, Deals, Contacts, or Companies. It is useful for automating the recording of important events, notes, or status updates directly into the Bitrix24 timeline associated with a specific entity.
Common scenarios include:
- Automatically logging system-generated messages or alerts related to a deal or lead.
- Adding manual notes or comments from workflows triggered by external events.
- Tracking changes or interactions in the CRM timeline for audit or collaboration purposes.
For example, a sales automation workflow could use this node to append a log entry every time a deal stage changes, helping team members stay informed within Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key. |
| Entity Type | The type of CRM entity to which the log message will be added. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the target entity (Lead, Deal, Contact, or Company) in Bitrix24. |
| Log Message Data | JSON-formatted data representing the content and details of the log message to add. |
| Options | Additional optional parameters including: |
| - Filter | JSON filter criteria (not typically used for adding logs). |
| - Order | JSON sort order (not typically used for adding logs). |
| - Start | Pagination start position (not typically used for adding logs). |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 after attempting to add the log message. This typically includes confirmation details about the created timeline entry.
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.
The node does not output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- Needs proper configuration of these credentials within n8n.
- Relies on Bitrix24's API endpoints to create timeline log entries.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured and the credentials are valid. OAuth2 tokens may expire and require refresh.
- Invalid Entity ID: Verify that the provided entity ID exists in Bitrix24 and matches the selected entity type.
- Malformed Log Message Data: The log message must be valid JSON and conform to Bitrix24's expected format; otherwise, the API call will fail.
- API Rate Limits or Permissions: Insufficient permissions or hitting API limits can cause failures. Check Bitrix24 user roles and API usage quotas.
- Error Messages: If the node throws an error, it will usually include the API error message. Use this to diagnose issues such as invalid parameters or network problems.