> 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/generic/other-operations/send-secure-function-keys.md).

# Send Secure Function Keys

This is a pre-built Action located under the **@Generic Element**. The functionality of this action in Avo Assure is to accept an encrypted text and send individual keystrokes to the applications element specified in the input. The result is stored in the given dynamic variable for further use during test execution.

## **Syntax**

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

| Argument                                | Description                                                                                                     |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| <p>\<encrypted Input><br>(Required)</p> | Encrypt the required value and provide the encrypted function key in the **Input Value** to perform the action. |

 **Output Value**: `<Dynamic Variable>(Optional);<Dynamic Variable>(Optional)`

| Argument                                                    | Description                                                       |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| \<Dynamic Variable>(Optional);\<Dynamic Variable>(Optional) | This dynamic variable stores the status as **True** or **False**. |

{% hint style="info" %}
**Note**: To use encrypted text as input for the **Send Secure Function Keys** action, you must first encrypt the required value using the AES Encryption feature available in the utilities section. For more information, [click here](/avo-assure/utilities/encryption.md).
{% endhint %}

### **Example: Sending Secure Function Key Input Using Encrypted Text**

In this example, we explain how to send a secure function key input to the application using encrypted text.

* **Action**: Send Secure Function Keys
* **Input Value**: Q/ELEbp38v/WZzyO6XAUIg==
  * The argument (**Q/ELEbp38v/WZzyO6XAUIg==**) represents the securely encrypted function key input that needs to be sent to the application
* **Output Value**: {Status}
  * The result of the secure key transmission is stored in the **{Status}** dynamic variable, with the following possible values:
    * **True**: If the secure function key is sent successfully.
    * **False**: If the secure function key is not sent successfully.
* **Logical Explanation**: The **Send Secure Function Keys** action reads the encrypted text from the **Input Value** column (**Q/ELEbp38v/WZzyO6XAUIg==**). The action sends the corresponding function key input securely to the target application element. After the secure input is processed. The outcome of this action (**True**) is stores in the **{Status}** variable.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FgguvWqlHZldmgqo3XfuD%2Funknown.png?alt=media&amp;token=32171509-f6aa-46c3-8880-38124cc72f2b" 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/generic/other-operations/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.