> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/actions/action-buttons/bulk-actions.md). # Bulk actions Learn how to enable your Noloco app users to trigger one-click actions in bulk. {% embed url="" %} Enable your team to move faster with bulk actions! Bulk actions allow you to select multiple records and run workflows, update fields, or delete records in bulk. How Bulk Action Buttons work: 1. Go to the Buttons section in your app’s view settings 2. Enable the “Bulk actions” toggle 3. Select the records you want to perform an action on 4. Choose the action button you’d like to apply to the selected records It’s that simple! Now you can run multiple workflows, update fields, or delete records with just a few clicks. Benefits of Bulk Action Buttons: * Save time: No need to perform repetitive actions on individual records anymore. * Improve efficiency: Streamline your workflows by processing multiple records at once. * Enhance flexibility: Apply the same action to multiple records in a single operation, making it easier to manage your data. Important to note: you can only enable bulk actions on your one-click action buttons. This feature does not work on modal pop-up action buttons. --- # 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://guides.noloco.io/actions/action-buttons/bulk-actions.md?ask=&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.