> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/backoffice-features/extra-creating-custom-components.md).

# Extra: Creating custom components

As you already know, Appmixer comes with a set of [Utilities](/kb/appmixer-studio-features/utility-modules.md) and Applications. These represent components that can be used when building a flow. By default, we offer a wide range of Utilities and Applications, and we're constantly working on adding new ones.

The beautiful thing about Appmixer is that you can develop your custom components using Node.js, and upload them to the Appmixer engine using our CLI tool. Alternatively, you can adjust the current components to your liking using the same method.

*Side note: Even though this is not one of the Backoffice features, it's rather about setting up your Appmixer instance, and therefore, related to Backoffice.*

Below, see a high-level overview of how you can develop and upload your own components. 

{% hint style="info" %}
We recommend referring to our technical documentation to learn more: <https://docs.appmixer.com/appmixer/appmixer-cli/appmixer-cli>
{% endhint %}

### 1. Define and implement your component

![](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-Mi0cHeA_CNdu-m2YvBF%2F-Mi0gVJ8BEgApzU7D-1f%2Fcustom-components-1.png?alt=media\&token=1d0ac55c-c9fb-44c6-add4-52f9934bb9e0)

### 2. Pack and publish using our CLI

![](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-Mi0cHeA_CNdu-m2YvBF%2F-Mi0gZ1hBgTKUjNoVak5%2Fcustom-components-2.png?alt=media\&token=3844666f-69df-47ba-a766-901cb112cabd)

### 3. Use it in your workflows and integrations

![](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-Mi0cHeA_CNdu-m2YvBF%2F-Mi0gfrnSlWzJSM195GA%2Fcustom-components-3.png?alt=media\&token=361879ef-8478-42e5-a4d4-b212536c2518)

As you – *or your developers* – can feel, the process does not take weeks or months as it's typical when building new APIs. Appmixer makes it super easy to implement new components fast and cost-effective.

{% hint style="info" %}
We recommend referring to our technical documentation to learn more: <https://docs.appmixer.com/appmixer/appmixer-cli/appmixer-cli>
{% 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.appmixer.com/kb/backoffice-features/extra-creating-custom-components.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.