Fireberry icon

Fireberry

Consume Fireberry API

Actions7

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 outdated transactions or logs.
  • Cleaning up test data after automated workflows.

Example: You have a list of record IDs representing obsolete customer orders and want to delete them all in one go rather than deleting each individually.

Properties

Name Meaning
Object Type Name or ID The Fireberry object type from which records will be deleted. Choose from a dropdown or specify an ID via expression.
Record IDs JSON array containing the IDs of the records to delete. Example format: {"data": ["recordId1", "recordId2"]}

Output

The output contains a JSON object representing the result of the batch delete operation. Typically, this includes confirmation of deletion or any error messages related to specific record IDs.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Fireberry API using an API key credential configured in n8n.
  • The node depends on internal methods that handle API requests to Fireberry, including fetching object types and fields dynamically.

Troubleshooting

  • Common issues:

    • Invalid or missing record IDs in the input JSON can cause partial or complete failure.
    • Incorrect object type selection may lead to errors if the object type does not exist or the user lacks permissions.
    • Network or authentication failures with the Fireberry API.

  • Error messages:

    • "The operation \"deleteBatch\" is not supported!" — indicates a misconfiguration or unsupported operation requested.
    • API errors returned from Fireberry (e.g., invalid IDs, permission denied) will be surfaced in the node output.

  • Resolutions:

    • Verify that the object type exists and is correctly selected.
    • Ensure the record IDs are valid and formatted as a JSON array under the data key.
    • Confirm API credentials are correct and have sufficient permissions.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion