Overview
This node integrates with Fireberry CRM (formerly Powerlink) to perform various operations on Fireberry objects dynamically. The "Query" operation allows users to retrieve records from any Fireberry object type using flexible filtering options, either through a visual query builder or by writing custom OData-style queries.
Common scenarios include:
- Extracting filtered lists of contacts, accounts, or custom entities for reporting or further automation.
- Paginating through large datasets with control over page size and number.
- Sorting results by specific fields.
- Using simple rule-based filters or advanced manual queries for complex data retrieval.
Practical example:
- Retrieve all active accounts where the status equals "Open" and sort them by creation date descending.
- Query a custom object with a complex filter string to get records updated after a certain date.
Properties
| Name | Meaning |
|---|---|
| Object Type | Select the Fireberry object type to work with (e.g., Account, Contact, or any custom object). |
| Return All | Whether to return all matching results or limit the output to a specified number. |
| Limit | Maximum number of results to return when "Return All" is enabled. |
| Page Size | Number of results per page when not returning all results. Must be between 1 and 100. |
| Page Number | The page number to retrieve when not returning all results. |
| Query Mode | Choose how to build your query: - Simple Query Builder: visually add rules with fields, operators, and values. - Advanced (Custom Query): write a raw OData-style query string manually. |
| Query Rules | (Shown only in Simple mode) Add one or more filtering rules: - Field: select a field to filter on. - Operator: comparison operator such as Equals, Not Equals, Greater Than, Contains, Is Null, etc. - Value: value to compare against (not required for null checks). - Combine With: logical AND/OR to combine multiple rules. |
| Query | (Shown only in Advanced mode) Enter an OData-style query filter string manually. Leave empty to fetch all records. |
| Fields | Comma-separated list of fields to return. Use * to return all fields. |
| Additional Options: Sort By | Field name to sort the results by. |
| Additional Options: Sort Type | Sort direction: Ascending or Descending. Defaults to Descending. |
Output
The node outputs JSON data representing the queried Fireberry records. The structure depends on the selected fields but generally includes an array of objects where each object corresponds to a record with key-value pairs for each requested field.
If pagination is used, the output contains only the records for the requested page unless "Return All" is enabled, in which case all matching records are returned.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for Fireberry CRM configured in n8n.
- Uses Fireberry's REST API endpoints for querying metadata and records.
- Network connectivity to Fireberry API endpoint is necessary.
- No additional external dependencies beyond the Fireberry API and n8n environment.
Troubleshooting
- Empty Results: Ensure that the Object Type is correct and that the query filters match existing data. For picklist fields, use exact text values as they appear in Fireberry.
- Invalid Query Syntax (Advanced mode): Custom OData queries must follow Fireberry's supported syntax. Refer to Fireberry documentation for valid operators and formatting.
- Field Loading Errors: If fields do not load in dropdowns, verify API credentials and network access.
- Pagination Issues: When not returning all results, ensure Page Size and Page Number are set correctly within allowed ranges.
- Error Messages: Common errors may include authentication failures (check API token), invalid object types, or malformed queries. Review error messages for hints and verify parameters accordingly.
- Mapping Errors: In simple query mode, ensure at least one query rule is defined; otherwise, no filter will be applied.
Links and References
- Fireberry API Documentation: https://developers.fireberry.com/docs/queries
- OData Query Syntax Reference (general): https://www.odata.org/documentation/odata-version-2-0/uri-conventions/