Actions11
Overview
This node integrates with the Fireberry API to manage records and metadata within Fireberry objects. Specifically, the Delete operation allows users to delete a single record from a specified Fireberry object type by providing the record's ID.
Common scenarios for this node include:
- Automating cleanup of outdated or invalid records in Fireberry.
- Integrating Fireberry data management into workflows where records need to be programmatically removed based on external triggers or conditions.
- Maintaining data hygiene by removing duplicates or erroneous entries.
For example, you might use this node to delete a customer record after they unsubscribe from a service or to remove test data created during development.
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 via expression. |
| Record ID | The unique identifier of the record to delete within the selected object type. |
Output
The output JSON contains the response from the Fireberry API after attempting to delete the specified record. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data 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 to load available Fireberry objects and their fields dynamically.
- Network access to Fireberry's API endpoint is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Record ID will cause the deletion to fail.
- Selecting an incorrect Object Type or one that does not contain the specified record will result in errors.
- Insufficient permissions or expired API credentials can prevent successful deletion.
Error messages:
"The operation "delete" is not supported!"— This indicates a misconfiguration or unsupported operation; ensure the operation parameter is set correctly.- API errors returned from Fireberry (e.g., "Record not found", "Unauthorized") should be checked and resolved by verifying input parameters and credentials.
Resolution tips:
- Double-check the Object Type and Record ID values.
- Verify that the API key credential is valid and has appropriate permissions.
- Use expressions carefully to ensure dynamic values resolve correctly.
Links and References
- Fireberry API Documentation (hypothetical link as no direct URL provided)
- n8n Expressions Guide
- n8n Node Development Documentation