Actions11
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 removal of data entries, such as cleaning up outdated or irrelevant records efficiently.
Practical examples:
- Deleting multiple customer records that are no longer active.
- Removing batches of transaction logs older than a certain date.
- Clearing out test data after a batch import.
Properties
| Name | Meaning |
|---|---|
| Object Type Name or ID | The Fireberry object type from which records will be deleted. Choose from a dropdown list or specify an ID via expression. |
| Record IDs | A JSON array containing the IDs of the records to delete in batch. |
Output
The output contains a JSON object representing the result of the batch deletion operation. It typically includes confirmation of which records were deleted or any errors encountered during the process.
No binary data output is involved in 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 deletions.
- The node uses internal methods to load available object types and validate record IDs.
Troubleshooting
Common issues:
- Providing invalid or empty record IDs will cause the deletion to fail.
- Specifying an incorrect or unauthorized object type may result in permission errors.
- Network or authentication failures can prevent successful API calls.
Error messages:
"The operation "deleteBatch" is not supported!"— indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- API errors related to authorization or invalid IDs will be returned from Fireberry and should be checked in the error message details.
Resolutions:
- Verify that the object type exists and you have permissions to delete records.
- Confirm that the record IDs are valid and formatted correctly as a JSON array.
- Ensure the API key credential is configured properly in n8n.
Links and References
- Fireberry API Documentation (hypothetical link)
- n8n Expressions Documentation
- n8n Node Development Guide