> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/customize-app/customize-a-screen/screen-actions.md).
# Screen Actions
## 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”.
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.
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.
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.
{% 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.
{% 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
### When this app needs automation
Use the normal instructions on this page when users only need to view, add, or update data. Use automation when the app needs to do something after that data changes, such as submit for approval, notify a reviewer, route work to a queue, start a conversation, update workflow status, or show a recoverable failure.
Good next steps:
* Automation Overview explains the full maker journey.
* Start From a Wizard is the safest way to create a guided workflow.
* Create your first approval workflow walks through a complete approval setup.
* Native Automation Screens explains Decision, Work Queue, Notification Center, Conversation, Workflow Status, Exception Resolution, Automation Launcher, Linked App Exchange, and Operator Console.
