# Build **Build** is the main entry point of the Platform, where the development cycle begins. From this page, you can: * Create and manage [pipelines](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/pipelines) in the **Pipelines** tab * Create and manage [capsules](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas) in the **Capsules** tab * Create and manage [globals](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/globals) variables in the Globals tab * Create and manage your [accounts](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/accounts) in the Accounts tab. ## **Pipelines tab**

Pipelines tab on the Build page.

A **pipeline** is an integration flow that connects systems and handles data exchange in the Digibee Integration Platform. It starts with a **trigger**, which starts the flow, and includes one or more **connectors** that interact with external systems, transform data, and allow communication between services. In the **Pipelines** tab of the Build page, you can: * Create a [pipeline from scratch](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/pipelines/how-to-create-a-pipeline) * Create a [pipeline based on an OpenAPI specification](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/pipelines/how-to-scaffold-a-pipeline-using-an-openapi-specification) * Create [projects to group and organize your pipelines](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/projects) ### **Search and filters** All pipelines you have access to are displayed in the center of the page. Use the following **filters** to quickly find and manage pipelines: * **Sort by:** * **Name:** Sort pipelines alphabetically. * **Last change:** Sort pipelines by most recent updates. * **Version:** Sort pipelines by most recent versions. * **Status:** * **All active:** Show only active (non-archived) pipelines. * **Archived:** Show only archived pipelines. * **Draft:** Show only undeployed pipelines. * **Triggers:** Filter pipelines by up to five selected triggers. {% hint style="info" %} Filters are reset when switching projects or realms. {% endhint %} ### **Pipeline card details**

Information and actions displayed in the pipeline card.

#### **Displayed information** * Category and trigger name used in the pipeline. * Pipeline name and description. * Number of steps, capsules, and subflows. * Pipeline version. * Deployed environments and their versions (hover to view all environments). * Pipeline preview (accessible via the **Preview** button, displayed only on hover). {% hint style="info" %} The pipeline preview is available only for pipelines saved after the feature release. For pipelines saved prior to the feature, you must save them again to view the preview. {% endhint %} #### **Actions available in the three-dot menu** * **New version:** Creates a new major version of the pipeline. * **Archive:** Archives the pipeline (cannot be permanently deleted). * **Restore:** Restores the pipeline if it has been archived. * **View history:** Displays the pipeline’s version history. * **View executions:** Opens the executions page in Monitor. * **Open Canvas:** Opens the pipeline in the development environment. ### **Moving a pipeline between projects** You can move pipelines between projects by dragging and dropping their cards to the desired project. Keep in mind that pipelines can only use accounts and globals associated with their current project. If you move a pipeline to a project where those accounts or globals are not available, it will no longer work and will not be possible to deploy. To fix this, you can either: * Update the [accounts](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/accounts) and [globals](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/globals) so they are available in the new project, or * Edit the pipeline to use accounts or globals already associated with the new project. ## **Capsules tab**

Capsules tab on the Build page.

Capsules are reusable sets of pre-configured connectors, encapsulated to speed up pipeline development while offering the same capabilities as individual connectors. In the **Capsules** tab of the Build page, you can: * Build capsules [customized to your use cases](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-configure-a-capsule) * Keep things organized with [capsule collections](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection) and [groups](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-group) * Easily access your capsules, including [archived ones](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-archive-and-restore-a-capsule) Capsules are listed on the left side of the Build page, next to **Pipelines**, and can be reused as connectors in your integration flows. {% hint style="info" %} Learn more in the [Capsules documentation](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/capsulas). {% endhint %} ## Globals tab

Globals tab on the Build page.

Globals are variables stored in the Platform that can be reused across multiple pipelines and capsules. After creating a global, you can reference it in any text field within connector configuration forms. When a global is updated, the change is automatically applied wherever the variable is used. In the **Globals** tab of the Build page, you can: * Create a global variable. * Visualize, edit and delete globals. * Access all globals, including deprecated ones. Learn more in the [Globals documentation](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/globals). ## Accounts tab

Accounts tab on the Build page

Accounts provide a secure way to store sensitive information, such as passwords, private keys, and authentication tokens, without exposing these credentials directly in your integrations. Furthermore, accounts can be restricted to specific projects, ensuring that sensitive information is only accessible where it is needed. They can then be used in connectors within pipelines and capsules to authenticate and authorize access to external endpoints. In the **Accounts** tab of the Build page, you can: * Create an account. * Visualize, edit and delete accounts. * Access all accounts, including deprecated ones. Learn more in the [Accounts documentation](https://docs.digibee.com/documentation/developer-guide/platform-administration/settings/accounts).