> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/reference/working-with-actions/bulk-create-rows-action.md).
# Bulk Create Rows
The Bulk Create Rows step allows you to create multiple rows in a table.
By default, the expected format of the action is an **array of objects** representing the rows to be created. The object *keys* are the column names and the *values* are the values to be inserted.
```javascript
{
name: "John",
age: 30
},
{
name: "Doe",
age: 28
}
```
This object will be sent to the server and converted to an `INSERT` statement, for example:
```sql
INSERT INTO users (name, age) VALUES ('John', 30), ('Doe', 28);
```
{% hint style="info" %}
You can check the action's *Payload* tab to see the objects sent to the server.
{% endhint %}
Unset fields will be presented as undefined and will not be used in the `INSERT` statement - the table defaults will be applied instead.
```javascript
{
id: 23,
created_at: "2022-10-21",
// this value will not be sent to the server
required_at: undefined,
}
```
You can always adjust the data before sending it and you can also add dynamic data to the query using Table variables - `{{ui.table.value}}`.
---
# 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://docs.uibakery.io/reference/working-with-actions/bulk-create-rows-action.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.
