> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/integrations/flows/module-header.md).
# Module Header
When adding or editing a module, regardless of the type (trigger, tool, etc.), the screen displays some standard items and resources in the header.
Here's what you'll find:
### **Name and Description**
At the top of the module editing screen, the header displays the module’s name and description.
You can rename any module, including the default modules in Skyone Studio. To do so, click on the name, make the desired changes, and press "Enter" or click outside the text box.
### **Execution configuration**
You can manage the number of executions of your module through this area.
To do this:
1. Choose the desired number and measure of time (seconds or minutes);
2. Determine the number of attempts;
3. Activate or deactivate the use of execution logs;
4. Click "**Save"** to finish the action.
### **Copy URL**
It is possible to copy the execution URL to run the flow outside of Skyone Studio, using a third-party application such as Postman.
### **Delete component**
You can delete the module, and a modal will be displayed to confirm the action.
{% hint style="warning" %}
It's not possible to undo the deletion.
{% 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 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.skyone.cloud/english/skyone-studio/integrations/flows/module-header.md?ask=&goal=
```
`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.