Overview
The node integrates with the Fireberry API to manage records of various object types. Specifically, the Delete operation allows users to delete a single record from a specified Fireberry object type by providing the record's ID.
This node is useful in automation workflows where you need to programmatically remove outdated or unwanted data entries from Fireberry. For example, it can be used to clean up customer records after account closure or to delete obsolete inventory items automatically.
Properties
| Name | Meaning |
|---|---|
| Object Type Name or ID | The Fireberry object type from which to delete the record. Choose from a dropdown list or specify an ID via expression. |
| Record ID | The unique identifier of the record to delete within the selected object type. |
Output
The output JSON contains the result of the delete operation for each input item. Typically, this will include confirmation that the record was deleted or details about the deletion status. If the operation fails and "Continue On Fail" is enabled, the output will contain an error message for the failed item.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Fireberry API.
- Requires an API authentication credential configured in n8n (an API key or token).
- Uses internal methods to load available object types and fields dynamically.
Troubleshooting
Common Issues:
- Providing an invalid or empty Record ID will cause the delete operation to fail.
- Selecting an incorrect or unsupported object type may result in errors.
- Network or authentication issues with the Fireberry API will prevent successful deletion.
Error Messages:
"The operation \"delete\" is not supported!"— This indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- Errors related to missing or invalid credentials — Verify that the API key/token is correctly configured.
"Record ID is required"or similar validation errors — Ensure the Record ID field is filled.
Resolution Tips:
- Double-check the Record ID and Object Type values.
- Confirm API credentials are valid and have sufficient permissions.
- Enable "Continue On Fail" if you want the workflow to proceed despite individual item failures.
Links and References
- Fireberry API Documentation (example placeholder link)
- n8n Expressions Documentation
- n8n Node Development Guide