Overview
The "Update Batch" operation of the Fireberry node allows users to update multiple records in a specified object type within the Fireberry system in a single execution. This batch update capability is useful when you need to modify several records at once, improving efficiency and reducing the number of API calls compared to updating records individually.
Typical use cases include:
- Bulk updating status fields for many records after a process completes.
- Correcting or enriching data across multiple entries simultaneously.
- Synchronizing changes from another system by applying updates in batches.
For example, you might update a batch of customer records to set a new subscription status or update product records with new pricing information all at once.
Properties
Name | Meaning |
---|---|
Object Type Name or ID | The Fireberry object type whose records you want to update. Choose from a dropdown list or specify an ID using an expression. This is required. |
Records | A JSON array of records to update. Each record must have an id field specifying the record's ID and a record object containing key-value pairs of fields to update. Format example: [{"id": "recordId", "record": {"FieldName": "New Value"}}] . |
Output
The node outputs an array where each element corresponds to the result of the batch update operation for the input item. The output JSON typically contains details about the updated records as returned by the Fireberry API. The exact structure depends on the API response but generally includes confirmation of updated record IDs and any relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Fireberry API via an API key credential configured in n8n.
- The node relies on Fireberry's REST API endpoints to perform batch updates.
- The "Object Type Name or ID" property dynamically loads available object types from Fireberry.
- Proper permissions on the Fireberry account are necessary to update records.
Troubleshooting
Common issues:
- Invalid or missing record IDs in the
recordsToUpdate
JSON will cause update failures. - Incorrect field names or values that do not conform to Fireberry schema may result in errors.
- Network or authentication issues with the Fireberry API can prevent successful updates.
- Invalid or missing record IDs in the
Error messages:
"The operation "updateBatch" is not supported!"
— indicates a misconfiguration or unsupported operation selection.- API error responses usually contain messages about invalid fields or permissions; check the Fireberry API documentation for specific error codes.
Resolution tips:
- Validate the JSON format and ensure each record has a valid
id
and corresponding fields. - Confirm that the API credentials are correct and have sufficient permissions.
- Use the Fireberry UI or API directly to verify object types and field names before configuring the node.
- Validate the JSON format and ensure each record has a valid
Links and References
- Fireberry API Documentation (hypothetical link)
- n8n Expressions Documentation
- n8n Node Development Guide