Overview
This node integrates with the Fireberry API to perform various data operations on Fireberry objects. Specifically, the Update operation allows users to update a single record of a specified object type by providing the record ID and the fields to modify.
Typical use cases include:
- Modifying existing records in Fireberry when data changes externally.
- Automating updates based on workflows, such as updating customer status or inventory levels.
- Syncing data from other systems into Fireberry by updating relevant records.
For example, you might update a "Contact" object’s phone number or change the status field of an "Order" object by specifying the record ID and new field values.
Properties
| Name | Meaning |
|---|---|
| Object Type Selected | A hidden boolean indicating if an object type has been selected (true if the "Object Type" parameter is not empty). |
| Object Type Name or ID | The Fireberry object type to update. Choose from a dropdown list loaded dynamically or specify an ID via expression. |
| Record ID | The unique identifier of the record to update within the selected object type. |
| Fields | A collection of fields to update on the record. For each field: - Field Name or ID: Select or specify the field to update. - Use Dropdown Values: Whether to select a value from predefined dropdown options. - Dropdown Value Name or ID: If using dropdown, select the value. - Field Value: The new value for the field (used if not selecting from dropdown). |
Output
The node outputs JSON data representing the result of the update operation. This typically includes the updated record details or confirmation of success. The exact structure depends on the Fireberry API response but generally contains the updated fields and metadata about the record.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry API.
- The node relies on dynamic loading methods to fetch available object types, fields, and dropdown values from Fireberry.
- Proper configuration of the Fireberry API credentials in n8n is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or empty Record ID will cause the update to fail.
- Selecting a field that does not belong to the chosen object type may result in errors.
- Using dropdown values incorrectly (e.g., not enabling "Use Dropdown Values" when required) can cause mismatched data errors.
- Network or authentication issues with the Fireberry API will prevent successful updates.
Error Messages:
"The operation "update" is not supported!"— indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- Errors related to missing or invalid parameters usually indicate required fields like Object Type or Record ID are not properly set.
- API errors returned from Fireberry will be passed through; check the message for details such as permission denied or invalid field values.
Resolution Tips:
- Double-check that the Object Type and Record ID are correct and exist in Fireberry.
- Verify that the fields to update are valid for the selected object type.
- Enable "Use Dropdown Values" only when updating dropdown fields and select appropriate dropdown values.
- Ensure the API key credential is valid and has sufficient permissions.
Links and References
- n8n Expressions Documentation
- Fireberry API documentation (refer to your Fireberry API docs for detailed field and object info)
- n8n documentation on creating custom nodes