> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/best-practices/modules/bulk-actions.md).
# Bulk actions
Bulk action modules can perform an action on multiple records in a single call.
To use bulk action modules, the user needs to create an array of records and map the array into the bulk module.
* In the bulk module UI, the mapping should always be turned ON by default.
* Types of output:
* If the response returns a single success / fail, the module should be an action module.
* If the response returns an output bundle of success / fail for an individual record, the module should be a search module.
* If possible, bulk modules should output the updated range/rows.
For more information for labeling and describing bulk action modules, see the best practices guide to [module labels](/custom-apps-documentation/best-practices/naming-conventions/modules/module-labels.md) and [module descriptions](/custom-apps-documentation/best-practices/naming-conventions/modules/module-descriptions.md).
---
# 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://developers.make.com/custom-apps-documentation/best-practices/modules/bulk-actions.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.