Actions7
- Custom Object Actions
Overview
This node enables interaction with Fireberry Custom Objects, specifically allowing batch deletion of multiple records within a specified custom object type. It is useful when you need to efficiently remove many records at once from a Fireberry database without deleting them one by one.
A practical example: Suppose you have a custom object "Contact" and want to delete several outdated contact records identified by their IDs in a single operation. This node's Batch Delete operation lets you specify those record IDs as a comma-separated list and deletes them all in one API call, saving time and reducing workflow complexity.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of the custom object to act on (e.g., Contact, Deal). |
| Record IDs | Comma-separated list of record IDs that you want to delete in this batch operation. |
Output
The output is a JSON array where each element corresponds to the result of the batch delete request. Each item typically contains data confirming the deletion status of the records requested. If an error occurs during the operation, the output may include an error message describing the failure.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Fireberry service.
- Depends on the Fireberry API endpoints for batch deleting records (
/api/v3/record/{objectType}/batch/delete). - Requires proper configuration of the Fireberry API credentials in n8n.
Troubleshooting
- Missing or invalid credentials: The node will throw an error if no valid API authentication token is provided. Ensure your Fireberry API credentials are correctly set up in n8n.
- Empty or invalid Record IDs: If the "Record IDs" property is empty, blank, or improperly formatted, the node throws an error indicating that at least one valid record ID is required.
- Unsupported resource or operation: The node only supports the "customObject" resource and specific operations including "batchDelete". Using unsupported values will cause errors.
- API errors: If the Fireberry API returns an error during the batch delete request, the node surfaces this as an error message. Check the API response and ensure the record IDs exist and you have permission to delete them.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output JSON.
Links and References
- Fireberry API documentation (for reference on batch delete endpoint and payload structure)
- n8n documentation on creating and using custom nodes and credentials