Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on CRM records dynamically across all supported object types. The "Delete" operation specifically allows users to delete a record of a selected Fireberry object type by providing the record's ID.
Common scenarios for the Delete operation include:
- Removing outdated or incorrect records from the CRM.
- Automating cleanup tasks in workflows where records need to be deleted based on certain conditions.
- Managing data lifecycle by programmatically deleting records after processing.
Example use case:
- A workflow that deletes a contact record from Fireberry CRM when the contact unsubscribes from a mailing list.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry object type to work with (e.g., Contact, Account, Lead). |
| Record ID | The unique identifier (ID) of the record to delete within the selected object type. |
Output
The node outputs JSON data representing the response from the Fireberry API after attempting to delete the specified record. This typically includes confirmation of deletion or any relevant metadata returned by the API.
No binary data output is produced by the Delete operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry CRM API.
- The node depends on the Fireberry API endpoints to perform CRUD operations.
- Proper configuration of the Fireberry API credentials in n8n is necessary.
- Network access to Fireberry's API endpoint must be available.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Record ID will likely result in an error from the API indicating the record was not found.
- Incorrect Object Type selection may cause the API call to fail or delete the wrong record.
- Missing or invalid API credentials will prevent successful communication with Fireberry.
Error messages and resolutions:
- "Record not found" — Verify the Record ID is correct and exists in the selected Object Type.
- Authentication errors — Check that the API key credential is correctly configured and has sufficient permissions.
- Network errors — Ensure that the n8n instance can reach the Fireberry API endpoint without firewall or proxy issues.