> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/actions/creating-an-action-that-triggers-data-edit.md). # Change Data ### Create Action Most of the time, when you want users to create new records in your database, you will take them to a screen with a [Form](/component-basics/forms-and-fields/how-to-create-and-edit-forms-and-fields.md) where they can fill out information about the record they are creating. However, sometimes you might want the user to click a button that automatically creates the new record without the user having to fill out a form. In the example below, a user is viewing details about a Trip they are planning and the app let's them add new Days to their Trip. Every time the user clicks the "+ DAY" button, another day is automatically added to their trip ![](/files/-LmjsybDtIRVfIqgUwzr) To configure your Create Action 1. Select the collection from your database that the Create Action will add a new record to 2. You will then be able to specify how all of the properties for the new record should be created. You can use an combination of Text, Magic Text, Numbers, and even Formulas for most properties. For relationships, you can select what they new record should be related to. In this example, we've specified that the new Day record should be related to the Current Trip the user is viewing. ### Update Action As with creating new records, updating a record is often done with a [Form](/component-basics/forms-and-fields/how-to-create-and-edit-forms-and-fields.md). However, there are times when you want the press of a button to automatically change the property on of a record, without the users having to manually make the changes in a form. In the example below, clicking a "Publish" button triggers an Update Action that automatically changes the current Trip's "Is Published" property from False to True. ![](/files/-LinUuG9bSG5oB_Zf3JG) To configure your Update Action 1. Select the available record that the Update Action will affect. 2. You will then be able to specify how all of the properties for that record should be changed. You can use an combination of Text, Magic Text, Numbers, and even Formulas for most properties. For relationships, you can select what they new record should be related to. 3. For properties that you don't want to change, you can simply leave them set as "No Change" ### Delete Action Delete actions are used to delete records from your database (no surprise there). They can be added to any kind of button as well as icons that are part other components like App Bars and Lists. ![](/files/-LjHR5aN3KpAGOFYvXhe) To configure your Delete Action, simply choose which record to delete. If the Delete Action is deleting an item inside of a List component, that row will be automatically removed from the list as soon as the user click the icon that you added the Delete Action to. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.adalo.com/actions/creating-an-action-that-triggers-data-edit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.