---
title: "Cloning a Playbook as a Component KB Article | ThreatConnect"
slug: "cloning-a-playbook-as-a-component"
description: "This article describes how to clone a Playbook as a Component in ThreatConnect."
updated: 2022-08-25T21:24:01Z
published: 2022-08-25T21:24:01Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.threatconnect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloning a Playbook as a Component

1. To clone a Playbook as a Component (i.e., convert an existing Playbook into a Component), click the vertical ellipsis ![](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/cloning-a-playbook-as-a-component-image-9b1569hd.png) at the upper-right corner of the **Playbook** **Designer** screen for the Playbook to be cloned, and select **Clone**. The **Clone Playbook** window will be displayed (Figure 1). ![Graphical user interface, application  Description automatically generated](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/cloning-a-playbook-as-a-component-image-uendkshx.png)
  - **Name**: By default, the name of the new Playbook will be **Copy of <*original Playbook name*>**. Click in the text box to edit the name of the Playbook, if desired.NoteWhen a Playbook is cloned, it is always named **Copy of *<original Playbook name>*** <original name="" playbook=""><em>&nbsp;</em>by default. If a Playbook has previously been cloned and its name was not edited (i.e., its name was saved as <strong>Copy of&nbsp;</strong><em><strong>&lt;original Playbook name&gt;</strong></em> <original name="" playbook="">), the name for any subsequent copies of the Playbook will need to be manually edited.</original></original>
  - **Please select a type**: Select **Component**.
  - Click the **CLONE**button.
2. If there is no Trigger in the Playbook being cloned, a Component Trigger will be added to it (Figure 2). If there is a Trigger in the Playbook being cloned, that Trigger will become a Component Trigger (Figure 3). ![A picture containing text  Description automatically generated](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/cloning-a-playbook-as-a-component-image-y96xkjzk.png)

![Diagram  Description automatically generated](https://cdn.document360.io/dfc206c8-1c9f-4725-b74d-a66f83432320/Images/Documentation/cloning-a-playbook-as-a-component-image-jlk7i5t6.png)

ImportantVariables in Triggers that have been converted to Component Triggers will be invalidated. They will need to be changed manually within the Apps that reference those variables in the new Component.

---

*ThreatConnect® is a registered trademark of ThreatConnect, Inc.*

20069-06 v.08.B