Overview
The 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.
This node is beneficial when you need to programmatically update records in Fireberry as part of an automated workflow, such as syncing data from other systems, correcting or enriching existing records, or applying batch updates conditionally.
Example use case:
You have a CRM system integrated with Fireberry, and when a contact's status changes in your CRM, you want to update the corresponding Fireberry record with new field values like "Status" or "Last Contacted Date".
Properties
| Name | Meaning |
|---|---|
| Object Type Selected | A hidden boolean indicating if an object type has been selected (true if objectType 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 | The name or ID of the field to update, selectable from a dynamic list based on the object type. |
| - Use Dropdown Values | Boolean flag indicating whether to select the field value from predefined dropdown options instead of entering free text. |
| - Dropdown Value Name or ID | If using dropdown values, select the specific dropdown option by name or ID, loaded dynamically depending on the object type and field. |
| - Field Value | The new value for the field if not using dropdown values. |
Output
The node outputs JSON data representing the result of the update operation for each input item. Typically, this includes confirmation of the updated record or any returned metadata from Fireberry about the update.
If the update fails for an item and "Continue On Fail" is enabled, the output for that item will contain an error message describing the failure.
The node does not output binary data.
Dependencies
- Requires an active connection to the Fireberry API via an API key credential configured in n8n.
- Uses dynamic loading methods to fetch available object types, fields, and dropdown values from Fireberry to populate property options.
- No additional external dependencies beyond the Fireberry API and n8n environment.
Troubleshooting
Common issues:
- Invalid or missing Record ID: Ensure the record ID exists and is correctly specified.
- Incorrect field names or IDs: Use the dynamic dropdowns to select valid fields to avoid typos.
- Dropdown value mismatch: When "Use Dropdown Values" is enabled, ensure the dropdown value corresponds to a valid option for the selected field.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
Error messages:
"The operation "update" is not supported!": This indicates an unsupported operation was requested; verify the operation parameter.- API errors returned from Fireberry will be passed through; check the error message for details such as permission denied, invalid field, or record not found.
Resolution tips:
- Use expressions carefully to ensure dynamic values resolve correctly.
- Enable "Continue On Fail" during testing to isolate problematic items without stopping the entire workflow.
Links and References
- n8n Expressions Documentation — for crafting dynamic expressions used in properties.
- Fireberry API documentation (refer to your Fireberry account resources) — for detailed API behavior and field definitions.