# Screen Actions

Screen actions let you automate what happens after someone submits a form. They’re perfect for updating default values to properties, routing users to the next step, or sending them to an external page — all without writing any code.

#### Available actions

1. **Change Data** - Update database properties automatically when the button is pressed.  

* Set text, number, toggle, relation, option properties.
* Choose whether the value should be an exact value or pulled dynamically (e.g., logged-in user).

Example: Set "Assigned To" to the logged-in user or mark a "Status" property as “Submitted”.<br>

2. **Go to Screen** - Navigate makers or end users to another screen inside the same app immediately after submit.

* Ideal for creating multi-step flows (e.g., submit → thank you screen).

3. **Open Link** - Redirect users to any external URL once the form finishes.

* Helpful for sending users to documentation, payment confirmations, or custom analytics pages.

{% hint style="info" %}
Important: If you enable either Go to Screen or Open Link, the other option is disabled.&#x20;

Change Data actions can be combined with one navigation action.
{% endhint %}

#### Step by Step Instructions

To use Screen Actions, follow these simple steps:

1. Open the app builder
2. Open a "Form (Add Item)"/"Form (Update One Item)" screen
3. Click the "+ Add Action" button to add a new action. A default action is added to the screen.

<figure><img src="/files/YNafhMANzlpfkTKydnSC" alt=""><figcaption></figcaption></figure>

4. Select the property on which you want to set a default value
5. Select the *value type* you want to set. i.e. "Fixed Value", "Logged In User" or "Current Day" etc.

<figure><img src="/files/KlU9FbvVNGchhWCKvDIr" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The *value type* is different based on the kind of property. For eg, only a *Date* property has a *value type* "Current Day". While *Title and Email* properties can have a *value type* as "Logged in User".
{% endhint %}

6. And finally, publish the app.

Now, if a user saves new or updated data through the app, their email address is automatically captured under the *Email* property, and the *Due Date* is set to 7 days from the day the data was saved.

{% hint style="info" %}
It's important to note that the "Logged in User" *value type* can only be used in private apps. To learn how to make your app private, please follow this link [Private apps](/users/private-apps.md).
{% endhint %}

Some common use cases for screen actions,

* Task Status: Set to "Not Started"
* Assigned To: Capture the logged-in user's email
* Delivery Date: Set to 7 days from the current date


---

# 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.notionapps.com/customize-app/customize-a-screen/screen-actions.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.