Actions7
- Custom Object Actions
Overview
This node enables interaction with Fireberry custom objects, specifically allowing operations such as querying, creating, updating, and deleting records within these custom objects. It is particularly useful for automating workflows that involve managing data stored in Fireberry's custom object system, such as CRM contacts, deals, or any user-defined entities.
For the Delete operation on a Custom Object, the node deletes a single record identified by its Record ID from a specified custom object type. This is beneficial when you need to programmatically remove outdated or incorrect records from your Fireberry database as part of an automated workflow.
Example use case: Automatically delete a contact record from Fireberry when it is marked as unsubscribed in another system.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of the custom object to act on (e.g., Contact, Deal). |
| Record ID | The unique identifier of the record to delete from the specified custom object type. |
Output
The output is a JSON array where each element corresponds to the result of the delete operation for each input item processed. For the Delete operation, the json output contains the response data returned by Fireberry after attempting to delete the specified record. This typically includes confirmation of deletion or details about the deleted record.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry API.
- The node uses HTTP POST requests to Fireberry's REST API endpoints to perform operations.
- Proper configuration of the Fireberry API credentials in n8n is necessary before using this node.
Troubleshooting
Missing Object Type or Record ID:
The node throws errors if the "Object Type" or "Record ID" properties are empty or missing for the Delete operation. Ensure these fields are correctly set.Invalid Credentials:
If no valid API credentials are provided, the node will fail with an authentication error. Verify that the Fireberry API key credential is configured and valid.API Errors:
Errors returned from the Fireberry API during deletion (e.g., record not found, permission denied) will be surfaced as node errors. Check the error message for details and verify the record exists and the API key has sufficient permissions.Empty or Malformed Record ID:
Providing an empty string or whitespace-only Record ID will cause an error. Make sure the Record ID is a valid non-empty string.Continue On Fail Behavior:
If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Fireberry API Documentation (Assumed URL for reference)
- n8n Documentation - Creating Custom Nodes
- REST API Concepts