# 2.6 Adding Actions to Your Page

Now that you understand the basics of the Page Data Model and Hooks, let's explore how to add actions to your page in BetterForms. This guide will walk you through the process of setting up and running actions.

## Introduction to Actions

Actions are instructions that tell the BetterForms framework to perform some operation. They can be used to create interactions with the user. Actions can be executed sequentially, and some actions block the execution of the next action until they are complete.

## Types of Actions

### Regular Actions

* ***showModal*** - Renders a modal dialog
* ***hideModal*** - Hides a modal that is non-blocking
* ***showAlert*** - Renders a toaster style alert
* ***path*** - redirects the user to a new page
* ***runUtilityHook*** - runs the `onUtility` hook passing it params
* ***downloadFile*** - downloads a file (link) to the user
* ***runOnCompleteHook*** - runs the `onComplete` hook
* ***clipboard*** - runs `clipboard` action allowing interaction with the clipboard
* ***cookie*** - Allows setting of browser side cookies
* ***wait*** - Waits for specified time or event
* ***emit*** - Vue event bus message emit
* ***scrollTo*** - Scrolls to an element
* ***namedAction*** - Runs a named action. Also requires the `name` key.
* ***function*** - Runs JavaScript

### Authentication Actions

* ***authLogin*** - Performs an authentication login
* ***authLogout*** - Performs logout
* ***authReset*** - Performs a password reset action
* ***authForgot** -* Performs a forgotten password reset hook
* ***authVerify*** - Performs a verification of the verify token
* ***authResend*** - Re/sends the email verification token
* ***authRegister*** - Performs a registration and if successful, runs the `onRegistrationHook`

## Where Actions Can Be Used

Actions can be injected in many places:

* Most hook scripts
* Navigation Menu Items
* Form action elements (buttons)
* Named Actions
* `*_actions` schema keys (where supported)

## Adding Actions to a Page

To add actions to a page, you can use the `actions` key in the page schema. This key can be either an object (for running a single action) or an array of objects (to run a series of actions).

### Example: Adding a Button with Actions

Here's an example of how to add a button with actions to your page:

```json
{
  "actions": [{
    "action": "showAlert",
    "options": {
      "text": "This is the alert message text",
      "title": "Hello World",
      "type": "information"
    }
  }],
  "buttonClasses": "btn btn-primary",
  "styleClasses": "col-md-4",
  "text": "Show Alert",
  "type": "button"
}
```

### Example: Adding a Named Action

You can also use named actions to define a set of actions that can be called from multiple places. Here's an example of how to define a named action:

```json
"namedActions": {
  "showCantDoThat": {
    "action": "showAlert",
    "options": {
      "title": "Whoooaa!!",
      "text": "You can't do that thing you just did.",
      "type": "warning"
    }
  }
}
```

## Next Steps

You now have a basic understanding of how to add actions to your page in BetterForms. As you build out your first application, you'll become more familiar with these components and how to use them effectively.

Explore the [BetterForms Elements reference](/reference/components-overview.md) to see the wide variety of available elements and their specific configuration options.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.klai.studio/getting-started/ide-quick-tour/first-app/adding-actions-to-your-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.