# Creating a Hyperflow

When you use a [**Hyperflow**](https://aisera.com/platform/hyperflows/), you designate the sources to integrate with, add **Functions**, and then specify information about the parameters that are required for that function/integration combination.

### **To create a Hyperflow:**

1. Choose **Hyperflows** from the left navigation menu in the Aisera Administration application.

   <figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FqDCYxLPrxfXrRi6HIJzE%2FUntitled%20Diagram-1744251830725.jpg?alt=media&#x26;token=a9ec36cd-c479-4320-a176-7b9215bd47bc" alt=""><figcaption></figcaption></figure>
2. Select the **+ New Hyperflow** button in the upper-right corner.
3. Fill in the **Name**, **Description**, and **Use Cases** parameters.
4. Click the **+ Add Functions** button.
5. In the **Add Functions** window, select an **Integration** from the drop-down menu.
6. Select **Actions** for your **Function** and click the **Next** button. \
   **Note:** You can choose more than one **Action**

   <div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FB54rY430GTJd9PV64DPJ%2Fimage.png?alt=media&#x26;token=2453fa3b-d21e-4883-8d7d-f93e4bd2e407" alt="" width="235"><figcaption></figcaption></figure></div>
7. Add [parameters for each of the **Actions**](https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/building-workflows/using-workflow-actions) that are part of the **Function**.&#x20;

   <div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FE9YoLrBQyU6X4OriZuDg%2Fhyperflow_action_parameters.png?alt=media&#x26;token=1917d30b-13b9-4662-a153-7443af2e3431" alt="" width="563"><figcaption></figcaption></figure></div>
8. While **Actions** support most interactions with supported external systems, **custom APIs** (Postman collections) can be imported to any Integrated and used as a Function.

   <div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2Funt7yfUbxCe33iMygFyy%2Fimage.png?alt=media&#x26;token=cfb5fa92-0000-403f-b7ea-1b6d9033545b" alt="" width="245"><figcaption><p>APIs can be imported to any integration<br></p></figcaption></figure></div>

   <div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FNFzCSKH2u9Um8FxYxIeS%2Fimage.png?alt=media&#x26;token=038ae24c-960b-456b-b8a1-d5b67089bd46" alt="" width="345"><figcaption><p>APIs can be imported using Postman collections<br></p></figcaption></figure></div>

   <div align="left"><figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FafawK2lSyJYvDbrMBIqT%2Fimage.png?alt=media&#x26;token=b207b593-2a7f-45d8-9a5a-c3fea01fb633" alt=""><figcaption><p>Integrations can have a mix of out-of-box Actions and custom APIs<br></p></figcaption></figure></div>
9. Additionally, any **Workflow** can be used as a **Function**. This gives you agentic automation limitless capabilities.
10. After you've added all of the parameters for your **Actions**, **APIs** or **Workflow** the **Function** is complete.

<figure><img src="https://3281977978-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvBFXjH9S1CAy9f5hzg5Q%2Fuploads%2FkIgDfXsKIHw7T84OGEU1%2Fhyperflow_final.png?alt=media&#x26;token=b9433f1d-4908-4ad0-afa6-386cce9eeafb" alt=""><figcaption></figcaption></figure>

### Registered Hyperflows now appear in the Used By Column of Workflows

You can register Hyperflows to associate them with a specific application or bot. The process to register a Hyperflow is the same as the process to register a Workflow. See [**Register a Workflow for Bot Conversational Triggers**](https://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/register-a-workflow-for-bot-conversational-triggers).\
\
Hyperflows appear in the **Used By** Column of Workflows.

<figure><img src="https://docs.aisera.com/~gitbook/image?url=https%3A%2F%2F2983236984-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FiZkLJr3EjXkd2tHYiQJP%252Fuploads%252FvfcJFuDHwMucmLd3bSWp%252Frn_6.png%3Falt%3Dmedia%26token%3D03ca7e62-bdeb-4069-8eca-f8485576a4a4&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=c81d26d6&#x26;sv=2" alt=""><figcaption></figcaption></figure>

#### **Hyperflows Validate Registration Before Deletion**

If you attempt to delete a registered Hyperflow (Hyperflow associated with a specific application/bot) you will receive the following message in the Aisera Admin UI: `This Hyperflow cannot be deleted because it is currently registered in the application. Please remove it from the Registered Flows before attempting deletion.`

### **Go Back Option in Hyperflows**

The **Go Back** option is now available for use in a Workflow when it is being executed through the Hyperflow.

## **Hyperflow Function Authentication (OAuth)**

**Hyperflows** includes the ability to execute the **API**s/**Actions/Workflows** associated with an integration as the user who is logged into the channel of interaction. For instance, if you are using the **Aisera Webchat** channel, the **Hyperflow** function authentication will be performed (OAuth) for the user logged into that channel.

## **Context Switching**

If the user switches context which is out of scope for the Hyperflow, the next best fulfillment will be used to respond to the user's request.

## Create a Hyperflow Using a Postman Collection

In addition to creating **Hyperflow** with the Aisera Admin UI, as discussed above, you can use Aisera's curated **Postman Collections** of to build Hyperflows.

Import, explore, and customize your data using Postman. Then, export your data and use the Aisera Admin UI to import it into your integrated systems for use with **Hyperflows**.
