# Create a package file

There is a simple way to create a package file:

1. copy and paste an existing file
   1. amend the *header*
2. Run `bc COMP GET /c <componentID1>, <componentID2>, ...`\
   and include all components that should become part of the package.

The output is ready to be used in your JsonC file: copy and paste.

```
--- COMP.GET ---
{"hint" : "Database Basics: Query Records without Batching (process)", "id" : "74c11026-6434-4ad2-8fda-f3f16053a9ec"},
  {"hint" : "Customer DB to Report FF (transform.map)", "id" : "0df30c6d-0c6f-4ffe-b0a2-8f843cd8094e"},
  {"hint" : "Customer Query (all) (connector-action#database)", "id" : "750076ca-31bd-4166-8606-e887e6690969"},
  {"hint" : "MS SQL Server Orders DB (connector-settings#database)", "id" : "c0b96c29-6f27-4934-885e-bdd68a9fca62"},

```

Please notice, by default, COMP GET retrieves all children, too: [GET](/boomi-console/commands/comp-components/fetch-get.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://boomi.markusschmidt.pro/boomi-console/library/packages/a-package-file/create-a-package-file.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.