# External orchestrators

> Connect an external orchestration engine and import its workflows as flows you can run from a blueprint

---

Site [llms.txt](/llms.txt)

---

Cloud Management Platform (CMP) supports two technologies: **HP Operations Orchestration** (HPOO) and **vCenter/vRealize Orchestrator**. Inputs defined on a flow appear on the order form.

<div class="alert alert-info" role="alert">


**External Orchestrators** is disabled by default and does not appear under **Admin**. Contact CloudBolt to enable it on your instance.
</div>


## Add an orchestrator

1. Go to **Admin** > **External Orchestrators**.
1. Select **Add**.
1. Choose the technology you are connecting to.
1. Fill in the connection details, then select **Continue**.
1. Give the orchestrator a **Name** and the folder or library path CMP should discover flows from, then select **Done**.

### Connection details

| Field | Description |
| --- | --- |
| **Scheme** | Protocol used to connect to the orchestration engine. |
| **Host** | IP address or hostname of the orchestrator. |
| **Port** | Port used to connect to it. The field is prefilled with the default port for the technology you chose. |
| **Account** | Username that runs the flows. |
| **Password** | Password for that account. |

### Name and flow location

| Field | Description |
| --- | --- |
| **Name** | The name this orchestrator is shown under in CMP. |
| **Base folder for discoverable flows** | The folder CMP imports flows from. It must contain the workflows themselves; subfolders are not searched. Some technologies label this field as a library path. |

## Edit an orchestrator

The **External Orchestrators** page lists each connection with its **Name**, **Technology**, **Username**, and **IP Address**. Select a name to open it. From there you can:

- **Edit Credentials.** Change the credentials used to authenticate the connection.
- **Edit Settings.** Change the name and the flow location.
- **Verify Connection.** Check that CMP can still reach the orchestrator.
- **Delete.** Remove the orchestration engine. Select **Remove** to confirm.

## Import flows

1. On the **External Orchestrators** page, select the name of your orchestrator.
1. Open the **Flows** tab.
1. Select **Import flows**.

## Run a flow from a blueprint

Once the connection is established and workflows are imported, add one to a blueprint.

1. Open **Catalog** and create or open a blueprint.
1. Open the **Build** tab.
1. Select **Action**.
1. Select **External Flow**.
1. Select **Create a new flow action now**.
1. Name the flow action, then select the target flow from the **Flow** dropdown.
1. Select **Save**.

The flow now runs whenever an order is submitted against that blueprint.

## Related

- [External flows](/docs/cmp/use/orchestration/actions/external-flows/): using an imported flow as an action.
- [Actions](/docs/cmp/use/orchestration/actions/): the other kinds of action a blueprint or trigger point can run.