Actions31
- Option Set Actions
- Public Query Actions
- Record Actions
- Role Actions
- Workflow Actions
- Worksheet Actions
Record → Create Batch
AI-generatedOverview
This node interacts with the HAP (Hyper Application Platform) API to create multiple records in a batch within a specified worksheet. It is useful when you need to insert many rows of data at once, improving efficiency compared to creating records one by one.
Common scenarios include:
- Bulk importing data from external sources into a worksheet.
- Automating data entry for large datasets.
- Synchronizing multiple records from other systems into HAP worksheets.
For example, you might use this node to upload a list of customer orders or inventory items all at once into a worksheet identified by its ID.
Properties
| Name | Meaning |
|---|---|
| Worksheet ID | The unique identifier of the worksheet where the records will be created. |
| Rows | An array of row objects to create. Each row contains fields with their IDs and values. |
| Trigger Workflow | Whether to trigger any associated workflow after the batch creation operation completes. |
Output
The node outputs JSON data representing the result of the batch creation operation. This typically includes details about the newly created records such as their IDs and any metadata returned by the HAP API.
If binary data were involved, it would be summarized here, but this operation deals only with JSON record data.
Dependencies
- Requires an API key credential for authenticating with the HAP API.
- Needs network access to the HAP service endpoint.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Worksheet ID: If the worksheet ID is incorrect or does not exist, the API will return an error. Verify the worksheet ID before running the node.
- Malformed Rows Data: Ensure the rows property is a valid JSON array with correctly structured field objects. Invalid JSON or missing fields can cause failures.
- API Authentication Errors: Check that the API key credential is set up correctly and has sufficient permissions.
- Trigger Workflow Option: If workflows do not trigger as expected, verify that the "Trigger Workflow" property is enabled and that workflows are configured properly on the HAP side.