> 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/web/table/send-function-keys-securely.md).

# Send Function Keys Securely

This is a pre-built Action located under the Table captured from the AUT Element, instructs the Avo Assure to accept an encrypted text and send the individual keystrokes to the application’s textbox within a scraped table and save the result in dynamic variable.

### **Syntax**

**Input Value:** `<Row>;<Col>;<Object Type>;<Index>;<Encrypted Text>`

| Argument                                  | Description                                         |
| ----------------------------------------- | --------------------------------------------------- |
| <p>\<Row></p><p>(Required)</p>            | Row number of the specified table cell              |
| <p>\<Col></p><p>(Required)</p>            | Column number of the specified table cell           |
| <p>\<Object Type></p><p>(Required)</p>    | Type of object inside the cell (e.g., textbox)      |
| <p>\<Index></p><p>(Required)</p>          | Element index of the object within the cell         |
| <p>\<Encrypted Text></p><p>(Required)</p> | Encrypted keystroke value to be sent to the textbox |

{% hint style="warning" %}
**Note:** The above syntax requires the user to specify the row and column of the target table cell, the object type, index, and the encrypted function key value to be sent.
{% endhint %}

**Output Value**

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

**Example**

**Sends encrypted keystrokes (e.g., function keys) to a textbox within a specified table cell.**

The **Send Function Keys Securely** action takes the input from the Input Value column (e.g., **2;5;input;1;u6llVGDU88P6XZcLQ0n9Q==**) and sends the decrypted keystroke value to the textbox located in the given cell. The result is stored in the **{Status}** variable, with possible values:

* **True** – if the keystrokes are sent successfully
* **False** – if the action fails or an error occurs

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FAlDbIsYiXAtRj6rPuGWJ%2Fimage.png?alt=media&amp;token=85551800-0903-40c4-b8fa-e1fb5edb900e" 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/web/table/send-function-keys-securely.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.