Copy timeline to another entity
The Copy timeline to another entity robot moves interaction history — activities (calls, emails, meetings, open channel chats, CRM forms, tasks) and comments — between leads, deals, contacts, companies, estimates, invoices and SPA items in Bitrix24 (Alaio). Source and target are set by type and ID; by default the source is the current item. It returns how many activities and comments were transferred.
The robot transfers a timeline between CRM entities and smart process items: the activity history — calls, emails, meetings, open channel chats, CRM form submissions, tasks — and comments. Source and target are set by type and ID; an empty source ID means the current item, so both directions work: a deal pulls the lead history after conversion, and a process on the old deal pushes history into a new one or into an SPA item. By default activities are attached: the record stays single and shows up in the target timeline in full — with the call recording, the email body and attachments; a repeated run creates no duplicates. A separate setting copies activities as independent universal to-dos instead. Comments are copied: the API cannot carry authorship, so the author name and date are prepended as the first line; attachments are downloaded and re-uploaded with a 25 MB per-file cap. One run transfers up to 500 activities and 200 comments; activities over the cap are counted as skipped, and only the first 200 comments are transferred. Typical uses: keep communication when a deal moves between pipelines, hand history to an after-sales smart process, gather the lead timeline in a deal.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Source: type | select | yes | current |
| Source: ID (empty = current) | int | — | |
| Source: SPA type ID | int | — | |
| Target: type | select | yes | deal |
| Target: ID (empty = current) | int | — | |
| Target: SPA type ID | int | — | |
| Transfer activities | bool | — | Y |
| Transfer comments | bool | — | Y |
| Activity transfer mode | select | — | bind |
| Filter: author (empty = everyone) | user | — | |
| Filter: from date | date | — | |
| Filter: to date | date | — | |
| Filter: count the period by (activities only) | select | — | created |
| Filter: only the last N records | int | — |
What does the robot return?
| Parameter | Type |
|---|---|
| Success (Y/N) | string |
| Activities transferred | int |
| Comments transferred | int |
| Skipped | int |
| Error | string |
What errors can the robot return?
The robot writes these messages to the business process log when it cannot complete a step. The text tells you what to fix in the settings or the data.
- Source and target cannot both be the current item
- Source and target are the same item
- Type, item ID or SPA type ID is missing
- Cannot resolve the current item: run the robot in a CRM or SPA item process
- Source or target not found, or no read permission
- Bitrix24 error during transfer, see the log for details
Scenario: move lead history into a deal after conversion
- Add the Copy timeline to another entity robot to deal automation
- Source: type Lead, ID — the deal's Lead ID field; target: Current item
- Keep activities and comments enabled, transfer mode — Attach
- After the run the lead history shows up in the deal timeline