> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/actions/desktop/textbox/send-secure-function-keys.md).

# Send secure function keys

This is pre-built action in Avo Assure and comes for **Captured Textbox Element** from **Desktop Application**. The functionality of the Avo Assure is to accept an encrypted text and send the individual keystrokes to the application’s element specified in the input.

### **Syntax**

**Input Value:** `<encrypted input>`

| Argument                                | Description                                            |
| --------------------------------------- | ------------------------------------------------------ |
| <p>\<encrypted input><br>(Required)</p> | Specify the encrypted text generated using Avo Assure. |

 **Output Value:**

| Argument                                                    | Description                                              |
| ----------------------------------------------------------- | -------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This variable stores the status as **true** or **false** |

{% hint style="warning" %}
***Note:** To provide encrypted text as input to the **Send Secure Function Keys** Action, the user should encrypt the required text using “**AES Encryption**” from the tool encryption utilities.*

*To navigate Encryption feature in Avo Assure then click* [*Learn more*](/avo-assure/utilities/encryption.md)
{% endhint %}

**Example**

**Sends secure function key input to the application using encrypted text**

The **Send Secure Function Keys** action takes the value from the Input Value column (e.g., Encrypted string - **CqIV+/BqoopwuD9O82Ixfg==**) is securely sent to the application as a function key input. For example, on a login page, you can use this encrypted password generated by **Avo Assure** for secure login.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FaUPv0NPmTgSKTzHdQ1MM%2Fimage.png?alt=media&amp;token=9cbcb048-ec6c-4eab-8f85-345ad5a468d6" alt=""><figcaption></figcaption></figure>


---

# 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.avoautomation.com/avo-assure/actions/desktop/textbox/send-secure-function-keys.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.