Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on Fireberry objects dynamically. Specifically, the Upload File operation allows users to attach a binary file to an existing record in Fireberry by specifying the record's GUID and the binary data field containing the file.
Common scenarios for this node include:
- Automating file attachments to CRM records, such as uploading contracts, invoices, or images related to a contact or account.
- Integrating external systems that generate files and need to store them within Fireberry records.
- Streamlining document management workflows by programmatically associating files with CRM entities.
Example use case:
- After generating a PDF report in a workflow, use this node to upload the PDF directly to the corresponding Fireberry record by referencing its ID and the binary data field holding the PDF.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry object type to work with (e.g., Contact, Account). |
| Record ID | The GUID of the specific record to which the file will be attached. |
| Input Binary Field | The name of the binary property in the input data that contains the file to upload. Common names: "data", "file", "attachment". This is case-sensitive. |
Output
The node outputs JSON data representing the response from the Fireberry API after uploading the file. This typically includes metadata about the uploaded file or confirmation of success.
If the node processes binary data (the file to upload), it expects the binary content in the specified input binary field but does not output binary data itself; instead, it returns JSON describing the upload result.
Dependencies
- Requires an API key credential for authenticating with the Fireberry API.
- Needs access to the Fireberry API endpoint URL configured in the credentials.
- Input data must contain the binary file data under the specified binary property name.
Troubleshooting
Common issues:
- Specifying a binary property name that does not exist or is misspelled in the input data will cause errors.
- Providing an invalid or empty Record ID will prevent the file from attaching correctly.
- Missing or incorrect API credentials will lead to authentication failures.
Error messages and resolutions:
- "Binary property not found" — Verify the exact name of the binary field in the input data and ensure it matches the "Input Binary Field" property.
- "Record ID is required" — Ensure the GUID of the target record is provided and valid.
- Authentication errors — Check that the API key credential is set up correctly and has sufficient permissions.
- API request failures — Confirm network connectivity and that the Fireberry API endpoint is reachable.