Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on CRM data objects dynamically. It supports creating, updating, deleting, retrieving, querying records, uploading files to records, and creating notes attached to records.
The Create operation specifically allows users to create new records of any Fireberry object type by mapping fields to the record's properties. This is useful for automating data entry into Fireberry CRM from other systems or workflows, such as adding new contacts, leads, or custom objects based on external triggers.
Practical example: Automatically create a new "Contact" record in Fireberry when a form is submitted on a website, mapping form fields like name, email, and phone number to the corresponding Fireberry fields.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry object type to work with (e.g., Contact, Lead, Account). |
| Columns | Map the fields to create the record. You can define field values manually or auto-map input data. |
- The Object Type property dynamically loads all available Fireberry object types.
- The Columns property uses a resource mapper to load and map fields specific to the selected object type. It supports adding all fields and refreshing the field list to get updated metadata.
Output
- The output JSON contains the newly created record's data as returned by the Fireberry API.
- Each item corresponds to one created record and includes all fields returned by the API after creation.
- No binary data is output for the Create operation.
Dependencies
- Requires an API key credential for Fireberry CRM to authenticate requests.
- Uses Fireberry REST API endpoints to fetch metadata and perform record creation.
- The node dynamically loads object types and fields via API calls to support flexible schema changes.
- Requires network access to Fireberry API endpoints.
Troubleshooting
Error: "Please map at least one field to create the record"
Occurs if no fields are mapped in the Columns property. Ensure you define at least one field value or enable auto-mapping from input data.Error: "No fields to create. Please map at least one field."
Happens if the mapped fields object is empty. Double-check your field mappings and input data.API request failures
Could be due to invalid credentials, network issues, or incorrect object type names. Verify API key validity and network connectivity.Field metadata loading errors
If fields do not load or refresh properly, check that the selected object type exists and the API user has permission to access its metadata.
Links and References
- Fireberry API Documentation
Official documentation for Fireberry CRM API endpoints and query syntax.
If you need details about other operations or resources, feel free to ask!