Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on CRM records dynamically across all supported object types. It allows users to create, update, delete, retrieve, and query records, as well as upload files and create notes attached to records.
A common use case is automating CRM workflows such as syncing data from other systems, bulk updating records based on external triggers, or retrieving specific record details for further processing. For example, you could use this node to fetch a contact record by its ID, update its phone number, or query all accounts with a certain status.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry object type to work with (e.g., Account, Contact). |
| Record ID | The unique identifier of the record to operate on (required for Get, Update, Delete). |
Output
The node outputs JSON data representing the result of the requested operation:
- For Get operation: Outputs the JSON representation of the retrieved record.
- For Create and Update operations: Outputs the JSON of the created or updated record.
- For Delete operation: Outputs confirmation or status of deletion.
- For Query operation: Outputs an array of records matching the query criteria.
- For Upload File operation: Outputs the response from the file upload API.
- For Create Note operation: Outputs the created note's details.
If binary data is involved (e.g., uploading files), the node handles binary properties accordingly but this is not relevant for the "Get" operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry CRM API.
- Needs network access to Fireberry's API endpoints.
- Uses internal helper functions to make HTTP requests to Fireberry's REST API.
Troubleshooting
- Missing or invalid Record ID: The "Get" operation requires a valid record ID. If omitted or incorrect, the node will throw an error indicating the record cannot be found.
- Invalid Object Type: Selecting an unsupported or misspelled object type may cause errors when querying metadata or records.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Empty Response: If the record does not exist or is inaccessible, the output may be empty or contain an error message.
- Network Issues: Connectivity problems to Fireberry's API will cause request failures; verify network and firewall settings.