> 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/editing-triggers-and-modules.md).

# Editing triggers and modules

All components added to the flow can be edited and deleted. In this documentation, we will explore in detail the process of editing and deleting triggers and modules after their initial addition and configuration in the flow.

### How to access <a href="#how-to-access" id="how-to-access"></a>

In the flow editing grid, note that when you click on any component - be it a trigger or modules, the screen shows three small icons: **copy** (link), **edit** and **delete**.

<figure><img src="https://2493694111-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQPcfIOA6Tl2Bmk6CdV2O%2Fuploads%2F8oU4tmMkO4zAIjWFc0U6%2Fediting-trigger-4.gif?alt=media&amp;token=30cd72ae-7b3a-4a88-815b-56b19154936e" alt=""><figcaption></figcaption></figure>

Below, you'll find each item:

{% tabs %}
{% tab title="Copy componenet" %}
When you click "**Copy"**, the component's URL will automatically be copied and you can share it with other people.

{% hint style="warning" %}
**Important:** if the person receiving this URL is not part of the workspace, they will not be able to view it.
{% endhint %}
{% endtab %}

{% tab title="Edit component" %}
If you need to edit a component of the flow, just click on "**Edit"**. The module's editing area will then open.

Edit as necessary and click "**Save"**.
{% endtab %}

{% tab title="Delete component" %}
If you need to delete a component from the flow, just click "**Delete"**. The modal will then open to confirm the deletion.

{% hint style="warning" %}
Although you can always add the deleted component again, any settings you have made will be lost.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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.skyone.cloud/english/skyone-studio/integrations/flows/editing-triggers-and-modules.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.
