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
The Bitrix24 node integrates with the Bitrix24 CRM and business platform, enabling users to interact programmatically with various Bitrix24 resources. Specifically, for the Timeline resource and the Get Bindings operation, this node retrieves binding information related to a specified CRM entity (such as Lead, Deal, Contact, or Company). This is useful for scenarios where you want to fetch all timeline bindings associated with a particular entity in Bitrix24, for example, to audit linked activities, communications, or other timeline entries.
Practical examples include:
- Fetching all timeline bindings for a deal to analyze its history.
- Retrieving bindings for a contact to understand interactions logged on their timeline.
- Automating reports or workflows based on timeline data linked to specific CRM entities.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Entity Type | The type of CRM entity to query timeline bindings for. Options: Lead, Deal, Contact, Company. |
| Entity ID | The unique identifier of the CRM entity whose timeline bindings are to be retrieved. |
| Return All | Boolean flag indicating whether to return all available results or only a subset. |
| Max Pages to Load | When not returning all results, limits the number of pages fetched. Each page contains up to 50 items. |
| Options | Additional optional parameters: - Filter: JSON object specifying filter criteria. - Order: JSON object specifying sort order. - Start: Number indicating start position for pagination. |
Output
The node outputs an array of items where each item's json property contains the timeline bindings data retrieved from Bitrix24 for the specified entity. The structure corresponds to the Bitrix24 API response for timeline bindings, typically including details about each binding such as binding IDs, types, and associated metadata.
If binary data were involved (not indicated here), it would represent files or attachments related to timeline entries, but this operation focuses on JSON data representing bindings.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Network access to Bitrix24 API endpoints.
- No additional external libraries beyond those bundled with the node.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect Entity ID or Entity Type causing empty or error responses.
- API rate limits or network connectivity problems.
- Malformed JSON in the "Filter" or "Order" options causing request failures.
Error messages:
- Authorization errors: Check that the API key, OAuth token, or webhook URL is valid and has sufficient permissions.
- "Entity not found" or similar: Verify the Entity ID and Entity Type are correct and exist in Bitrix24.
- JSON parse errors: Ensure that any JSON input in filter/order fields is well-formed.
- Pagination limits exceeded: Adjust "Max Pages to Load" if too many pages are requested.