> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/systems-builder.md).

# Systems Builder

System Builder allows the user to build a new private system to connect and use in the workflows. Private systems are accessible only inside the project and cannot be accessed elsewhere. 

This page displays both old and new private systems available in the project. It also displays the recommended version of the system set during publishing. If no published version is available, the draft or deprecated version will be shown.

{% hint style="info" %}
Old systems are marked with an “Old” label.
{% endhint %}

### **Show System Usage**

This option displays the credentials connected to the system and lists the workflows which are using it.

{% hint style="success" %}
The Delete option is not yet introduced for new system versions. It will be released in the upcoming releases.
{% endhint %}


---

# 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.dckapintegrator.com/project-manager/systems-builder.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.