> For the complete documentation index, see [llms.txt](https://studio.docs.ai.vonage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio.docs.ai.vonage.com/voice/nodes/actions/stop-recording.md).
# Stop Recording
The **Stop Recording** node can be used in conjunction with either the [Start node](https://studio.docs.ai.vonage.com/voice/nodes/start-node) or the [Start recording node](https://studio.docs.ai.vonage.com/voice/nodes/actions/start-recording). It enables you to strategically stop recording at any point of the conversation allowing you to keep user data private.
If you choose to use this node as part of your agent, the reports for the agent will feature only one type of recording i.e. from the beginning of the call (or Start recording node if you have it enabled)
{% hint style="info" %}
*Once you have selected a point in the flow where you want to stop recording please note that you cannot choose to start recording the call again. You will, however, be able to see the transcription of the full call. You can only use 1 Stop recording node within your virtual assistant.*
{% endhint %}
### Here’s how to use it:-
**Drag and Drop the node to the desired location in the flow**
Drag and drop the Stop Recording node from the Toolbar onto the canvas. Connect it to wherever you want to stop the call recording.
You can use this node multiple times in the flow including subflows.
---
# 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://studio.docs.ai.vonage.com/voice/nodes/actions/stop-recording.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.