Actions11
Overview
The Fireberry node allows users to interact with the Fireberry API to manage records and metadata within Fireberry objects. Specifically, the "Update" operation updates an existing record of a specified object type by modifying one or more fields.
This node is beneficial in scenarios where you need to programmatically update data stored in Fireberry, such as synchronizing external data sources, automating record maintenance, or integrating Fireberry with other systems.
Example use cases:
- Updating customer information in Fireberry when changes occur in a CRM.
- Modifying status fields on project records based on workflow progress.
- Correcting or enriching data fields automatically after validation or enrichment steps.
Properties
| Name | Meaning |
|---|---|
| Object Type Name or ID | The Fireberry object type whose record you want to update. You can select from a list of available object types 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, you specify: - Field Name or ID (selectable from the object's fields or via expression) - Whether to use dropdown values - Dropdown Value Name or ID (if using dropdown) - Field Value (if not using dropdown) |
Output
The node outputs JSON data representing the updated record returned from the Fireberry API. This typically includes the record's fields with their new values after the update operation.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Fireberry API via an API key credential configured in n8n.
- The node depends on Fireberry API availability and correct permissions for updating records.
- Uses internal methods to load options dynamically for object types, fields, and dropdown values.
Troubleshooting
Common issues:
- Invalid or missing Record ID will cause the update to fail.
- Specifying fields that do not exist on the chosen object type will result in errors.
- Using dropdown values incorrectly (e.g., selecting a value not valid for the field) may cause failures.
- Network or authentication issues with the Fireberry API will prevent successful updates.
Error messages:
"The operation "update" is not supported!"— indicates a misconfiguration or unsupported operation requested.- Errors related to invalid field names or IDs usually mean the field does not belong to the selected object type.
- Authentication errors suggest problems with the API key credential setup.
Resolutions:
- Verify the Record ID is correct and exists.
- Use the dynamic dropdowns to select valid object types and fields.
- Enable "Use Dropdown Values" only for fields that support dropdowns and select valid dropdown options.
- Check API credentials and network connectivity.
Links and References
- Fireberry API Documentation (example placeholder link)
- n8n Expressions Documentation
- n8n Node Development Guide