Overview
The node provides integration with the Fireberry API, allowing users to perform various operations on Fireberry objects. Specifically, the Update Batch operation enables updating multiple records of a specified object type in a single execution. This is useful when you need to modify several records at once, improving efficiency compared to updating records one by one.
Typical use cases include:
- Bulk updating customer or product information after receiving new data.
- Applying status changes or corrections to multiple records simultaneously.
- Synchronizing data from external sources where batch updates are more performant.
For example, you might update a batch of contact records to change their subscription status or update inventory quantities for multiple products in one go.
Properties
| Name | Meaning |
|---|---|
| Object Type Name or ID | The Fireberry object type to update records for. Choose from a dropdown list or specify an ID via expression. |
| Records | JSON array of records to update. Each record must have an id (record ID) and a record object containing field-value pairs to update. Format example: [{"id": "recordId", "record": {"Field1": "Value1", ...}}]. |
Output
The node outputs the result of the batch update operation as JSON. Typically, this will include confirmation of updated records or any returned metadata from the Fireberry API about the update process.
If the node supports binary data output (not indicated here), it would represent related file or media content associated with the records, but this operation focuses on JSON data updates only.
Dependencies
- Requires connection to the Fireberry API using an API key credential configured in n8n.
- The node depends on Fireberry's REST API endpoints for object metadata and record manipulation.
- It uses internal methods to load available object types and fields dynamically.
Troubleshooting
- Invalid Object Type: If the selected object type does not exist or is misspelled, the node will fail. Ensure the object type is correctly chosen from the dropdown or specified accurately via expression.
- Malformed Records JSON: The
Recordsproperty must be valid JSON with the correct structure (idandrecordkeys). Invalid JSON or missing required fields will cause errors. - API Authentication Errors: Missing or incorrect API credentials will prevent successful communication with Fireberry.
- Partial Failures: If some records fail to update, the node may throw errors unless "Continue On Fail" is enabled, which allows processing other records while reporting errors per item.
- Unsupported Operation Error: If the operation parameter is set incorrectly, the node throws an error indicating the operation is unsupported.
To resolve these issues:
- Verify object type and field names.
- Validate JSON syntax and structure for records.
- Confirm API credentials are properly set up.
- Use "Continue On Fail" cautiously to handle partial failures gracefully.
Links and References
- Fireberry API Documentation (hypothetical link)
- n8n Expressions Documentation
- n8n Node Development Guide