> 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/appmixer-studio-features/visual-features/renaming-a-component.md).

# Renaming a component

[In the last section, we spoke about the importance of a clear naming convention. Now that you know how to rename a flow](/kb/appmixer-studio-features/visual-features/renaming-a-flow.md), let's look at a simple way to rename a component. That's right, even the pre-built components can be renamed so that your flow is clear to you or/and your colleagues even after months from the launch.

{% embed url="<https://youtu.be/Qam3PYuiRuE>" %}
Renaming a component
{% endembed %}

Start by opening a flow and clicking on the component that you want to rename.

![Open a flow and click on the component that you want to rename](/files/-MfDieeaU1MCdBPIfs5u)

Do you see the "pen" icon on the right? Nice! Click it... Now, you can insert a new name of the component and, thus, keep your flow organised for yourself and/or your colleagues.

![Click on the "pen" icon on the right, and rename the component](/files/-MfDjRSoXycqSOjqSH-y)

Congrats! 🎉 You learned about all the core visual features of the Appmixer Studio. Next, you'll learn about the power of Utility modules.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.appmixer.com/kb/appmixer-studio-features/visual-features/renaming-a-component.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.