> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-save-a-capsule.md).

# How to save a Capsule

Learn how to fill out the form to save the Capsule in the Digibee Integration Platform.

Follow these steps to save a Capsule:

1. Click the **Save** button in the upper right corner of the Capsule environment.
2. In the **Capsule title** field, enter the title of the Capsule to be displayed in the Capsules list.&#x20;
3. The **Capsule name** field is filled in automatically, but can be edited if necessary. The name is generated from the title you entered in the previous field and is the identifier of the Capsule.

{% hint style="warning" %}
The name of the Capsule must be unique within the collection. Therefore, it’s not possible to have more than one Capsule with the same name in the same [collection](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection.md), even if they are in different [groups](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-group.md).
{% endhint %}

1. Add a description in the **Capsule description** field.
2. Select the icon that will represent the Capsule inside the group.
3. Select the collection to which you want to add the Capsule. If you don’t have a [collection created](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection.md), the Capsule is saved in the **Default collection**.
4. Select the group to which you want to add the Capsule. If you don’t have a [group created](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-group.md), the Capsule is saved in the **Default group**.

{% hint style="info" %}
You can change the collection and group of a Capsule after you have saved it. Learn more in [How to change a Capsule collection and group](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-change-a-capsule-collection-or-group.md).
{% endhint %}

8. See what the Capsule icon looks like in the **Capsule preview**.
9. Click **Save**.

<figure><img src="https://content.gitbook.com/content/jvO5S91EQURCEhbZOuuZ/blobs/pNEAjgO7Rc8uL8dn043l/save-capsule.gif" alt=""><figcaption></figcaption></figure>

Saving the Capsule doesn’t make it available in the list of Capsules in the pipeline. To make it available, you must [publish the Capsule](/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-publish-a-capsule.md).

Capsules that are not yet published have the **Development** tag in the Capsules page.

<figure><img src="https://content.gitbook.com/content/jvO5S91EQURCEhbZOuuZ/blobs/UYtOoETTmdDSt6NJ20WV/save-capsule-2.png" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-save-a-capsule.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
