Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on CRM records dynamically across all supported object types. Specifically, the Update operation allows users to update fields of an existing record by specifying the record ID and mapping the fields to be updated.
Common scenarios for this node include:
- Automating updates to customer or contact records when new information arrives.
- Synchronizing data between Fireberry CRM and other systems by updating records programmatically.
- Bulk updating records based on external triggers or workflows.
For example, you could use this node to update a contact's phone number or status field after receiving new data from a form submission or another application.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry CRM object type to work with (e.g., Account, Contact). Loaded dynamically. |
| Record ID | The unique identifier (ID) of the record to update. |
| Columns | Map the specific fields to update on the record. Only these fields will be changed. Supports manual mapping or auto-mapping input data. |
Output
The node outputs JSON data representing the updated record as returned by the Fireberry API. This typically includes the updated fields and their new values.
No binary data output is produced by the Update operation.
Dependencies
- Requires an API key credential for Fireberry CRM configured in n8n.
- Uses Fireberry REST API endpoints to perform record updates.
- Dynamic loading of object types and fields depends on Fireberry metadata endpoints.
Troubleshooting
Error: "Please map at least one field to update"
Occurs if no fields are mapped in the Columns property. Ensure you define at least one field to update.Error: "No fields to update"
Happens if the mapped fields object is empty. Verify that your mapping contains valid fields and values.Invalid Record ID
If the provided Record ID does not exist or is malformed, the API will return an error. Double-check the ID format and existence.API Authentication Errors
Make sure the API key credential is correctly set up and has sufficient permissions.Field Mapping Issues
If fields do not appear or cannot be mapped, try refreshing the field list via the UI menu to reload metadata.