> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/19.latest/add-ons/forms/actions.md).

# Actions

Reference for the actions contributed by the Umbraco.Forms.Automate add-on.

The Forms add-on contributes the following actions.

## Submit Form

Alias: `umbracoForms.submitForm`. Programmatically submit a form entry from inside an automation. Pick the form to submit to and provide values for its fields.

## Export Form Entries

Alias: `umbracoForms.exportEntries`. Read entries from a form. The action returns the entries as a collection that downstream steps can iterate over with a **For Each** node.

The action reads entries from the Forms database, so an entry submitted a moment before the run is included. Each entry holds only the form's current fields. Fields removed from the form are not exported.

Sensitive data follows the rules of the Forms backoffice export. A field marked as containing sensitive data is exported only when the workspace service account is in the **Sensitive data** user group. Without that access, sensitive values read `This value is hidden.`, and each entry's `memberKey` is `null`.

{% hint style="warning" %}
Exported values pass through Umbraco Automate's run history and logs. Add the service account to the **Sensitive data** user group only when that is acceptable for your site.
{% endhint %}

{% hint style="info" %}
Open the step in the canvas to see each action's settings and output fields.
{% endhint %}


---

# 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.umbraco.com/umbraco-automate/19.latest/add-ons/forms/actions.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.
