Importing from a link

Open the link provided by the sender. Before confirming, review package contents and transfer specifics. You need management permissions for every package resource type in the destination project.

Review the plan and copy

The recipient opens the import page. The cabinet loads the package name and contents and lists only eligible target projects—projects where the recipient can manage every package resource type.

1. Expand Package items.
2. Select the target project.
3. Select Review and copy. The cabinet first builds the plan and opens it in a separate dialog; copying has not started yet. Build plan inside the expanded package contents opens the same dialog in advance.
4. Review every plan row and the repeated-copy warning, then select Copy to project.

Each plan row has an action and an explanation of what will happen to the resource:

• Create makes a new independent copy of the named resource;
• Use existing links the package to a resource already present in the target project;
• Configure after copying creates the resource but requires a follow-up in the cabinet, such as selecting a keyword channel, message recipient, or agent channels again;
• Conflict identifies an incompatible match, such as a different variable type or schema;
• Skip leaves the resource uncopied.

When copying to another project, a landing, delivery, or automation incoming-message trigger keeps its specific channel selection without switching to all channels. The plan and result show Configure after copying: select suitable target-project channels in the copied resource settings before publishing or starting it. All channels remains the general mode. An agent subscription page with specific channels is copied without a publication until its channels are configured.

Every confirmation creates new independent copies for items marked Create, even when the same link has already been imported into that project. Review the plan before repeating the action: a previous import does not automatically turn new items into updates of the earlier copies.

After import starts, a background process dialog opens. The result separately counts created, existing, skipped, setup-required, and failed items; setup-required and failed items include per-resource messages.

If import does not start

Check that:

1. the address contains the full token parameter;
2. the link is active and has not expired;
3. there is at least one target project where the user can manage every package resource type;
4. a target project is selected;
5. the message in the error block above the form: the UI displays plan and import errors there.

If the process has already started, its state and ID are available in the progress dialog and in Processes.

Lead and dialog variables are transferred as definitions, without individual customer or conversation values. When these fields are included in an agent package, the agent's access settings for the transferred fields are preserved too. Working with dialog variables in the destination project requires the corresponding permissions.