FireberryTest icon

FireberryTest

Consume Fireberry API Test

Overview

This 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 its record ID. This is useful in scenarios where you need to remove outdated or incorrect data entries programmatically within an automated workflow.

Practical examples include:

  • Automatically deleting user accounts or entries when they are marked as inactive.
  • Removing obsolete inventory items from a database after stock depletion.
  • Cleaning up test or temporary records created during data processing.

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 using an 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 confirm whether the deletion was successful or provide error information if it failed.

If the node supports binary data output (not indicated here), it would represent any associated files or attachments related to the deleted record, but this node focuses on JSON responses only.

Dependencies

  • Requires an active connection to the Fireberry API via an API key credential configured in n8n.
  • The node depends on internal methods to fetch available object types and fields dynamically.
  • Network access to Fireberry's API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty Record ID will cause the deletion to fail.
    • Selecting an incorrect or unsupported object type may result in errors.
    • Network or authentication failures can prevent the API call from succeeding.
  • Error messages:

    • "The operation "delete" is not supported!" — indicates an unsupported operation was requested; ensure the operation parameter is set correctly.
    • API errors returned from Fireberry typically include messages about missing permissions, invalid IDs, or connectivity issues.
  • Resolutions:

    • Verify that the Record ID exists and belongs to the selected object type.
    • Confirm that the API key credential has sufficient permissions to delete records.
    • Check network connectivity and Fireberry service status.

Links and References

Discussion