Overview
The node integrates with the Fireberry API to perform various data operations on Fireberry objects. Specifically, the Delete Batch operation allows users to delete multiple records of a specified object type in one request. This is useful for bulk cleanup or removal of outdated or unwanted data entries.
Typical use cases include:
- Removing multiple user accounts or contacts at once.
- Deleting batches of obsolete records from a database.
- Automating data maintenance tasks where many records need to be purged simultaneously.
For example, if you have a list of record IDs representing old transactions, you can pass them to this node's Delete Batch operation to remove all those transactions in a single workflow step.
Properties
| Name | Meaning |
|---|---|
| Object Type Selected | A hidden boolean indicating whether an object type has been selected (true if selected). |
| Object Type Name or ID | The Fireberry object type to operate on. Choose from a dropdown list or specify an ID via expression. |
| Record IDs | JSON array containing the IDs of the records to delete in batch. Example format: {"data": ["id1", "id2"]} |
Output
The node outputs JSON data representing the result of the batch delete operation. Typically, this will confirm which records were successfully deleted or provide error details if any deletions failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry API.
- The node depends on Fireberry's REST API endpoints to perform batch deletion.
- The node uses internal methods (
executeDeleteBatchOperation) defined in its bundled dependencies to handle the API calls.
Troubleshooting
Common issues:
- Providing invalid or non-existent record IDs may cause partial or complete failure of the batch delete.
- Not selecting or specifying the object type correctly will prevent the operation from running.
- Insufficient permissions or expired API credentials can lead to authentication errors.
Error messages:
"The operation \"deleteBatch\" is not supported!"— indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- API errors returned from Fireberry (e.g., unauthorized, not found) will be surfaced as node execution errors.
Resolutions:
- Verify that the object type and record IDs are correct and exist in Fireberry.
- Check that the API key credential is valid and has necessary permissions.
- Use the "Continue On Fail" option to handle partial failures gracefully.
Links and References
- Fireberry API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- n8n Node Development Guide