> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/chat-flow/workflow-management/create-new-flow/view-and-retrieve-deleted-nodes-from-the-archive-section.md).
# Delete and restore nodes
## **Delete nodes**
1. Select the node on your canvas.
2. In the panel on the right, in the top right corner, click the bin icon.
{% hint style="info" %}
This will remove the node **and all subsequent nodes that were connected to it** from your flow.
{% endhint %}
## **View deleted nodes**
When you select a workflow, a number is shown in brackets next to the bin icon at the bottom of your list of flows. This indicates the number of nodes that have been deleted from this flow.
Click the recycle bin to bring up a panel displaying all the parent nodes that were deleted from the selected flow as well as the children nodes connected to them.
## **Restore deleted nodes**
To restore a node that you've previously deleted, drag and drop the node from the Recycle Bin onto a placeholder node in the canvas.
{% hint style="success" %}
You can select to restore only the parent node or to restore the parent node with all its children nodes.
{% endhint %}
{% embed url="" %}
---
# 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://help.clickatell.com/chat-flow/workflow-management/create-new-flow/view-and-retrieve-deleted-nodes-from-the-archive-section.md?ask=&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.
