Link Open Channel conversation
The Link Open Channel conversation robot ties Open Lines dialogs (client chats) from one CRM entity to another — for example, from a lead to a deal. The correspondence appears in the target entity's timeline. Inputs are the type and ID of the source and target entities and a mode: all dialogs, the last one, or only unfinished ones. It returns how many conversations were found and linked.
The robot makes an Open Lines conversation visible on the CRM entity you need without losing it on the source. An Open Lines dialog is stored in the timeline as an activity (PROVIDER_ID = IMOPENLINES_SESSION); the robot finds those activities on the source entity and binds them to the target via CRM activity bindings. The binding is added, not moved: the source keeps the dialog and the target gains it in its own timeline. Inputs are the type (lead, deal, contact, company) and ID of the source and target entities, plus a mode — link all dialogs, only the last one, or only unfinished (open) dialogs. Outputs: how many dialogs were found, how many were linked, how many were already linked, the list of activity IDs, and a success flag (Y/N). A typical scenario is to surface a lead's correspondence on the deal it became, so the manager sees the full conversation history on the deal card. The robot needs no chat-module permissions — CRM rights are enough.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Source entity type | select | yes | LEAD |
| Source entity ID | int | yes | |
| Target entity type | select | yes | DEAL |
| Target entity ID | int | yes | |
| Which conversations to link | select | yes | all |
| Action | select | yes | link |
What does the robot return?
| Parameter | Type |
|---|---|
| Conversations found | int |
| Linked | int |
| Already linked | int |
| Detached from source | int |
| Activity IDs (comma-separated) | string |
| Success (Y/N) | 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.
- Error: specify a valid type and ID for both the source and target entity
- Error: the source and target are the same entity
- API error
Scenario: show a lead's correspondence on the deal
- A lead had an Open Lines conversation and a deal was created from it
- The Link Open Channel conversation robot in All dialogs mode binds the lead's dialogs to the deal
- The correspondence appears in the deal timeline and the linked count is returned to the process