> 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/telephony/set-param.md).
# Set Parameter
Set a parameter value at any point in the conversation flow.
You can use the Set Parameter node when you are looking to have a set value for a parameter - and don’t want the caller to fill it in. We can either input the value manually or use a placeholder sign "$" and the name of the parameter you are referring to ("$PARAMETER\_NAME).
You can add multiple parameters to the node by clicking on "Add parameter".
## Best Practices - When to use Set Parameter?
### Influence the conversational flow
You can use the set param to tag that the user went through a specific part in the flow, and do a condition so he won’t go through it again.
For example, if the user is has got to the “missed” tab in the classification node, we can set a parameter that lets us know it was triggered once, and add a condition that has a different logic:
**Steps:**
1. Create a parameter and set a value in the set param node.
2\. Create a condition node that if the parameter has a value/is equal to the value you set in the set param node.
3\. Attach the “missed” in the classification node to the condition node.
4\. Attach the “default” to the logic you want the user to go first.
5\. Attach it to the set param node.
6\. Attach the set param node to the original classification node.
7\. Attach the condition you created to the logic you want the user to go to the second time.
### Set a specific parameter, not the user input
Another use case you can use the set param node is when you need to set a specific parameter after an intent (in the classification node) and not the user’s input. For example, when the parameter values need to be the same from all callers.
All you need to do is to attach the set param node after the intent and set the value you want.
Usually, we set the intent’s name as the value of the parameter.\
---
# 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/telephony/set-param.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.