Package Information
Available Nodes
Documentation
@bines/n8n-nodes-fireberry
This is an n8n community node for Fireberry CRM (formerly Powerlink).
Fireberry is an Israeli CRM platform designed for medium-sized businesses.
n8n is a fair-code licensed workflow automation platform.
β¨ Version 3.0 - Full Dynamic Support with ResourceMapper
v3.0 introduces advanced features with full dynamic field support including lookup fields:
- π― Universal Node - One node for ALL Fireberry objects (not just Account, Contact, Case, Task)
- π Dynamic Object Discovery - Automatically loads all available objects from your Fireberry account
- π Smart Field Loading - Fields are loaded dynamically with proper types
- π Dynamic Lookup Fields - Dropdown selection for related records (Contacts, Users, Accounts, etc.)
- π Dynamic Picklist Fields - Dropdown selection for status, categories, and other picklist values
- π ResourceMapper Integration - Modern n8n field mapping with auto-complete and field matching
- π Future-Proof - Works with new objects and fields without updates
Installation
Follow the installation guide in the n8n community nodes documentation.
Community Nodes (Recommended)
- Go to Settings > Community Nodes.
- Select Install.
- Enter
@bines/n8n-nodes-fireberryin Enter npm package name. - Agree to the risks and select Install.
Manual Installation
To use this node, install it locally:
npm install @bines/n8n-nodes-fireberry
Credentials
You need a Fireberry account to use this node.
Get your API Token:
- Log in to your Fireberry account
- Click the gear icon (Settings) β Integration
- Go to API Forms
- Copy your Token ID
Features
π― Dynamic Object Type Support
Choose from all available objects in your Fireberry account:
- ΧΧ§ΧΧ (Account/Customer)
- ΧΧΧ© Χ§Χ©Χ¨ (Contact)
- Χ§Χ¨ΧΧΧͺ Χ©ΧΧ¨ΧΧͺ (Case)
- ΧΧ©ΧΧΧ (Task)
- ΧΧ©ΧͺΧΧ© (User)
- Χ§ΧΧ€ΧΧΧ (Campaign)
- ΧΧΧΧ Χ (Order)
- ΧΧ¦Χ’Χͺ ΧΧΧΧ¨ (Quote)
- ...and any other objects in your Fireberry account!
π Smart Field Types
The node automatically handles all field types with appropriate UI controls:
- String - Text input fields
- Number - Numeric input with validation
- Phone - Phone number fields
- Email - Email address fields with validation
- URL - Website URL fields
- Textarea - Long text/notes fields
- Date - Date picker
- DateTime - Date and time picker
- Picklist - π₯ Dropdown with values from Fireberry
- Lookup/Reference - π₯ Dropdown with related records (Users, Contacts, Accounts, etc.)
- File/Document - File attachments
π Dynamic Lookup Fields (NEW!)
Lookup fields automatically display available records in a dropdown:
- Primary Contact (primarycontactid) β Shows all Contacts
- Account Owner (ownerid) β Shows all Users
- Parent Account (parentaccountid) β Shows all Accounts
- Campaign (campaignid) β Shows all Campaigns
- Any custom lookup field β Automatically loads related records!
Example:
When creating an Account:
- Select "ΧΧΧ© Χ§Χ©Χ¨ Χ’ΧΧ§Χ¨Χ" (Primary Contact)
- Choose from dropdown: "ΧΧ ΧΧΧΧ ΧΧΧ", "Χ ΧΧ ΧΧΧ¨ ΧΧΧ‘Χ£", "Amit Bines", etc.
- The correct Contact ID is automatically used
π Dynamic Picklist Fields
Picklist fields automatically display available options:
- Status β Shows: ΧΧΧ©, ΧΧͺΧΧΧΧ, ΧΧ§ΧΧ Χ€Χ’ΧΧ, etc.
- Category β Shows your custom categories
- Priority β Shows priority levels
- Any custom picklist β Automatically loads values!
Supported Operations
All operations work with any object type in your Fireberry account:
π Create
Create a new record with ResourceMapper for easy field mapping:
- Auto-complete field names
- Proper field type validation
- Dynamic dropdowns for picklists and lookups
- Support for custom fields
- Automatic exclusion of auto-generated primary keys
βοΈ Update
Update an existing record by ID:
- Specify only the fields you want to change
- Same dynamic field support as Create
- ResourceMapper for easy updates
ποΈ Delete
Delete a record by its ID.
π Get
Retrieve a single record by its ID with all fields.
π Query
Execute advanced queries with two modes:
π― Simple Query Builder (NEW in v3.5!)
Visual query builder similar to Make/Integromat:
- Field Selection - Dropdown of all available fields from your Object Type
- Operator Selection - Choose from: Equals, Not Equals, Greater Than, Less Than, Greater or Equal, Less or Equal, Is Null, Is Not Null, Starts With, Ends With, Contains
- Value Input - Enter the value to compare
- AND/OR Logic - Combine multiple rules with AND or OR
- Auto-Generated Query - Query string is built automatically
βοΈ Advanced (Custom Query)
Write custom OData query strings manually for complex scenarios:
- Return All - Automatically paginate through all results
- Limit - Specify maximum number of results
- Page Size - Control results per page
- Sorting - Sort by any field (ascending/descending)
- Field Selection - Choose specific fields or use
*for all
π Upload File
Upload files and attachments to any Fireberry record:
- Works with any object type (Account, Contact, Case, Task, etc.)
- Supports all file types
- Proper MIME type detection
- Handles binary data from form submissions, HTTP requests, and other sources
- Endpoint:
POST /api/v2/record/{objectid}/{recordid}/files
Note: Check docker logs to see available binary field names if you encounter errors.
π Create Note
Create notes attached to records or standalone:
- Note Text - Supports plain text and HTML formatting
- Related Record - Optionally attach to any record (Account, Contact, etc.)
- Parent Note - Create threaded replies to existing notes
- Works with Object Type codes for flexible record linking
- Endpoint:
POST /api/record/note
Query Modes
Simple Query Builder
Perfect for common filtering scenarios. Build queries visually:
Example 1: Find active customers with email
Rule 1: statecode = 0 (Combine with AND)
Rule 2: emailaddress1 Is Not Null
Result: statecode eq '0' and emailaddress1 ne null
Example 2: Find accounts starting with 'Χ' OR 'Χ'
Rule 1: accountname Starts With 'Χ' (Combine with OR)
Rule 2: accountname Starts With 'Χ'
Result: startswith(accountname, 'Χ') or startswith(accountname, 'Χ')
Advanced Query Syntax
Fireberry supports powerful OData query operators:
eq- Equalne- Not equalgt- Greater thanlt- Less thange- Greater than or equalle- Less than or equaland- Logical ANDor- Logical ORnull- Check for NULLne null- Check for NOT NULLstartswith- String starts withendswith- String ends withcontains- String contains
Advanced Query Examples:
accountname eq 'ΧΧΧ¨Χͺ ΧΧΧΧΧ'
idnumber eq '123456789' and telephone1 ne null
emailaddress1 ne null or telephone1 ne null
accountname startswith 'Χ'
createdon gt '2025-01-01' and statuscode eq 1
Examples
Example 1: Create a Customer with Contact
Object Type: ΧΧ§ΧΧ (Account)
Operation: Create
Fields:
- accountname: "ΧΧΧ¨Χͺ ΧΧΧΧΧΧ ΧΧ’Χ΄Χ"
- idnumber: "123456789"
- telephone1: "03-1234567"
- emailaddress1: "info@example.co.il"
- primarycontactid: [Select from dropdown: "ΧΧ ΧΧΧΧ ΧΧΧ"]
- ownerid: [Select from dropdown: "Amit Bines"]
Example 2: Query Active Contacts (Simple Query Builder)
Object Type: ΧΧΧ© Χ§Χ©Χ¨ (Contact)
Operation: Query
Query Mode: Simple Query Builder
Query Rules:
Rule 1:
- Field: emailaddress1
- Operator: Is Not Null
- Combine With: AND
Rule 2:
- Field: statecode
- Operator: Equals (=)
- Value: 0
Return All: Yes
Fields: firstname,lastname,emailaddress1,mobilephone1,accountname
Sort By: lastname
Sort Type: Ascending
Alternative using Advanced mode:
Query Mode: Advanced (Custom Query)
Query: emailaddress1 ne null and statecode eq 0
Example 3: Update Case Status
Object Type: Χ§Χ¨ΧΧΧͺ Χ©ΧΧ¨ΧΧͺ (Case)
Operation: Update
Record ID: {{$json["caseid"]}}
Update Fields:
- statuscode: [Select from dropdown: "Χ€ΧͺΧΧ¨"]
- resolutionnotes: "Issue resolved successfully"
Example 4: Create Task Assigned to User
Object Type: ΧΧ©ΧΧΧ (Task)
Operation: Create
Fields:
- subject: "Follow up with customer"
- description: "Call regarding quote"
- ownerid: [Select from dropdown: "Amit Bines"]
- accountid: [Select from dropdown: "ΧΧΧ¨Χͺ ΧΧΧΧΧΧ"]
- duedate: "2025-10-10"
Technical Details
Field Type Detection
The node uses Fireberry's metadata API to determine field types:
GUID β Field Type
b4919f2e-2996-48e4-a03c-ba39fb64386c β Picklist (Dropdown)
a8fcdf65-91bc-46fd-82f6-1234758345a1 β Lookup (Related Record)
6a34bfe3-fece-4da1-9136-a7b1e5ae3319 β Number
ce972d02-5013-46d4-9d1d-f09df1ac346a β DateTime
... and more
Lookup Field Loading
For each lookup field, the node:
- Fetches field metadata to determine target Object Type
- Queries target Object Type for all records
- Uses PrimaryKey and PrimaryField from API response
- Displays records in dropdown with proper names and IDs
Example: For primarycontactid (Primary Contact field):
- Detects it's a lookup to Object Type 2 (Contacts)
- Queries all Contacts
- Displays: "ΧΧ ΧΧΧΧ ΧΧΧ (fc7af7af-...)", "Amit Bines (682a84b8-...)"
- Uses correct contactid when creating/updating
Migrating from v2.x
What's New in v3.0:
- β ResourceMapper for better field mapping UI
- β Dynamic dropdown support for Picklist fields
- β Dynamic dropdown support for Lookup fields
- β Improved field type detection
- β Better error handling
Migration is Seamless:
- All v2.x workflows continue to work
- Field names remain the same
- New features available immediately for new nodes
Additional Resources
- Fireberry API Getting Started Guide - Official REST API documentation
- Fireberry Developer Documentation - Complete developer guide
- n8n Documentation - Learn more about n8n workflow automation
Support
If you encounter any issues or have questions:
- Check the Fireberry API Documentation
- Review the n8n Community Nodes Guide
- Open an issue on GitHub
Changelog
v3.9.2 (2025-10-02)
- π§Ή Cleanup: Removed unnecessary debug logs
- Removed console.log from Create, Update, and Query operations
- Kept Upload File logs for troubleshooting binary field names
- Cleaner production code
- π Documentation: Complete English update
- Added comprehensive operations documentation (Upload File, Create Note)
- Added Additional Resources section with official Fireberry links
- Added Disclaimer section
- Improved operation descriptions with emojis
- Better structure and readability
v3.9.1 (2025-10-02)
- π FIX: Upload File debug logging
- Added console logs to show available binary field names
- Helps troubleshoot "binary field not found" errors
- Improved field description with common names hint
- Logs show: available fields vs. requested field name
v3.9.0 (2025-10-02)
- π NEW: Upload File operation - Upload files to any record
- Upload files via
/api/v2/record/{objectid}/{recordid}/files - Supports all file types with proper MIME type handling
- Works with any Fireberry object (Account, Contact, Case, etc.)
- Upload files via
- π NEW: Create Note operation - Create notes attached to records
- Create standalone notes or attach to any record
- Supports HTML formatting in note text
- Optional: Reply to existing notes (parent note ID)
- π§ FIX: Auto-generated primary key fields excluded from Create
- Automatically removes primary key fields (e.g.,
activitylogid) when creating records - Prevents "Bad request" errors when using resourceMapper UI
- Works for all object types dynamically via metadata
- Automatically removes primary key fields (e.g.,
v3.8.0 (2025-10-02)
- π― MAJOR FIX: Query with multiple fields now works!
- β Fixed Fireberry query syntax based on official documentation
- π Each condition now wrapped in parentheses:
(field = value) - π€ Combine operators uppercase:
AND/ORinstead ofand/or - π§ Correct operators:
is-null,is-not-null,start-with,end-with - π Added documentation link - click "Docs" button in node
- π Query example:
(statuscode = 6) AND (originatingleadcode = 9)
v3.7.5 (2025-10-02)
- π Enhanced debug logging for Query troubleshooting
- π Logs show: rules data, built query, API request body
- π Investigating "OR vs AND" issue in Simple Query Builder
- π‘ Use:
docker logs -f <container> | grep "Query"
v3.7.4 (2025-10-02)
- β Search now works in "Add field to send" dropdown!
- π Fixed: Removed
removeListSearch: truethat was blocking search - π Fields now sorted alphabetically for easier navigation
- π n8n's built-in search now available in field selection
v3.7.3 (2025-10-02)
- π Query Fix: Improved handling of multiple rules
- β combineOperation defaults to 'and' if not specified
- π Debug log shows built query for troubleshooting
- π Search in resourceMapper works by default (n8n built-in feature)
- π― Query with 2+ fields should now work correctly
v3.7.2 (2025-10-02)
- π Critical Fix: Update operation now works correctly
- β Changed resourceMapper mode from 'update' to 'add'
- β Fixes "No field that can be used for matching found" error
- π Update uses Record ID field (already exists), no matching needed
- π Debug logs remain active for troubleshooting
v3.7.1 (2025-10-02)
- π Debug logs for Update operation - troubleshoot Update issues
- π Logs show: recordId, columnsData, body to send, API URL
- π Investigating "Bad request" errors in Update
- π Query is independent of columns - can split to separate nodes safely
v3.7.0 (2025-10-02)
- π― Simplified Query Builder - Back to reliable manual input
- β Removed problematic "Value Type" dropdown (wasn't working in fixedCollection)
- β Simple string input for all value types - works reliably
- π Improved hints: explains how to find exact Picklist values
- π‘ Workaround: Use Create/Update operation to see available Picklist values, then copy to Query
- π Fixed: Query Builder now works consistently for all field types
- π Kept debug log for query building (helps troubleshooting)
v3.6.2 (2025-10-02)
- π Debug Version: Added detailed console logging for Picklist dropdown
- π Troubleshooting "No data" issue in Picklist Value dropdown
- π Logs show: objectType, fields count, Picklist fields found, values loaded
- π οΈ Temporary debug version to identify the root cause
v3.6.1 (2025-10-02)
- π Critical Fix: Picklist dropdown now loads values correctly
- β¨ Uses dedicated API endpoint for each Picklist field
- β¨ Properly loads all available Picklist values from Fireberry
- π― Each Picklist field queried individually for accurate data
v3.6.0 (2025-10-02)
- π Major Feature: Picklist dropdown support in Query Builder!
- β¨ New "Value Type" option: "Enter Manually" or "Select from Picklist"
- β¨ Picklist dropdown shows all available options from all Picklist fields with [Field Name] prefix
- β¨ Manual entry still available for text, numbers, dates, and GUIDs
- π Fixed multiple rules query building (added debug logging)
- π¨ Improved UX for building queries with Picklist values
v3.5.6 (2025-10-02)
- π Critical Fix: Smart value formatting for different data types
- β¨ Numbers now work correctly (no quotes:
123instead of'123') - β¨ Dates now work correctly (no quotes:
2025-01-01instead of'2025-01-01') - β¨ GUIDs work correctly (with quotes:
'fc7af7af-...') - β¨ Text/strings work correctly (with quotes:
'ΧͺΧ ΧΧΧΧ') - π― Auto-detection of value type using regex patterns
v3.5.5 (2025-10-02)
- π Critical Fix: Changed Value field back to string input (was blocking manual entry)
- β¨ Value now supports manual text entry for all field types
- β¨ Added helpful placeholder and hints for Picklist and Lookup fields
- π Improved instructions: recommends checking Create/Update dropdowns for available values
- π¨ Better UX for text/number/date fields
v3.5.4 (2025-10-02)
- π Critical Fix: Fixed operator dropdown triggering Expression mode (again!)
- π Fixed Value dropdown not loading options
- β¨ Value dropdown now shows all Picklist and Lookup values with field labels
- β¨ Added "[Field Name]" prefix to help identify which field each value belongs to
- β¨ Added "Enter manually" option for text/number fields
- π¨ Improved operator mapping (equalβ=, notEqualβ!=, etc.)
v3.5.3 (2025-10-02)
- π Major Feature: Dynamic Value dropdown in Query Builder!
- β¨ Value field automatically detects Picklist and Lookup fields
- β¨ Picklist fields show dropdown with options (e.g., "Χ€ΧͺΧΧ", "Χ‘ΧΧΧ¨")
- β¨ Lookup fields show dropdown with related records (Contacts, Accounts, Users)
- β¨ Smart field type detection using metadata
- π¨ Same UX as Create/Update operations!
v3.5.1 (2025-10-02)
- π Critical Fix: Fixed query operators to use Fireberry's correct syntax (
=,!=,>,<instead ofeq,ne,gt,lt) - π Fixed "One or more operators are invalid" error in Simple Query Builder
- β¨ Added helpful description for lookup field values in queries
- π Improved placeholder text for query values
v3.5.0 (2025-10-02)
- π Major Feature: Visual Query Builder!
- β¨ Simple Query Builder mode - Build queries visually like Make/Integromat
- β¨ Field dropdown with all available fields from Object Type
- β¨ 11 operators: Equals, Not Equals, Greater Than, Less Than, Greater or Equal, Less or Equal, Is Null, Is Not Null, Starts With, Ends With, Contains
- β¨ AND/OR logic between rules
- β¨ Auto-generated OData query strings
- β¨ Advanced mode for custom queries (backward compatible)
- π¨ Improved UX for query building
v3.4.1 (2025-10-02)
- π¨ Added helpful description hints for "Refresh Field List" option
- π Improved UX guidance for resourceMapper
v3.3.10 (2025-10-02)
- π Major Feature: Dynamic dropdown support for Lookup fields!
- β¨ Lookup fields now display related records in dropdown (Contacts, Users, Accounts, etc.)
- β¨ Automatic PrimaryKey and PrimaryField detection for all Object Types
- β¨ Support for all lookup field types with proper record display
- π Fixed resourceMapper options display with
removeListSearch: true - π¨ Improved UI for field selection
v3.0.0 (2025-10-02)
- π Major Update: ResourceMapper integration
- β¨ Dynamic Picklist field support with dropdown values
- β¨ Improved field type detection
- β¨ Better error handling and validation
- π¨ Modern n8n UI with auto-complete
v2.0.0 (2025-10-02)
- π BREAKING CHANGE: Complete architectural restructure
- β¨ Dynamic object type selection from Fireberry metadata API
- β¨ Support for ALL Fireberry objects
- β¨ Dynamic field loading based on selected object
- β¨ Support for 11 different field types
v1.0.0 (2025-10-01)
- π Initial release
- β Support for Account, Contact, Case, Task
- β CRUD operations
- β Advanced Query with pagination
License
Disclaimer
This project is provided "as is", without any warranty of any kind, express or implied. Use it at your own risk.
The purpose of this repository is to share knowledge and provide tools for the community. The maintainers are not responsible for any issues, damages, or losses caused by the use of this code.
For the official Fireberry API documentation, please refer to: π https://developers.fireberry.com/docs/getting-started
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Support
For issues, questions, or feature requests, please open an issue on GitHub.