Fireberry icon

Fireberry

Consume Fireberry API

Actions11

Overview

The Fireberry node allows querying records from the Fireberry API. It supports flexible query construction either through a visual query builder or by writing advanced query strings directly in Fireberry's query syntax. This node is useful for retrieving data from Fireberry objects with fine-grained filtering, sorting, and field selection.

Common scenarios include:

  • Fetching specific records based on complex conditions.
  • Retrieving only selected fields to optimize data processing.
  • Sorting and limiting results for pagination or reporting.
  • Returning each record as an individual item for further workflow processing.

Example use cases:

  • Query all contacts where the email field is not empty and sort them by last modified date.
  • Retrieve product records with price greater than a certain value using an advanced query string.
  • Use the visual query builder to filter leads created within a date range and return their names and statuses.

Properties

Name Meaning
Object Type Name or ID The Fireberry object type to query (e.g., "Contact", "Product"). Choose from a list or specify an ID via expression.
Fields Names or IDs List of fields to return for each record. Select from available fields or specify IDs via expression.
Query Type Method to create the query:
- Visual Query Builder: build query using UI controls.
- Advanced Query: write raw Fireberry query syntax string.
Query Fireberry query string for advanced queries, e.g. ((field1 = value1) and (field2 is-not-null)). Only shown if Query Type is "Advanced".
Flattened Query Builder For visual query builder mode: a collection of query items representing field conditions and logical group separators (AND/OR). Allows building complex queries visually.
Sort By Name or ID Field to sort the results by. Choose from available fields or specify an ID via expression.
Sort Type Sort order: Ascending or Descending.
Record Limit Maximum number of records to return. Leave empty to return all matching records.
Show Real Value Whether to show real values instead of only IDs for dropdown and lookup fields.
Return as Items If true, returns each record as a separate output item instead of an array. Useful for workflows that process records individually.

Output

The node outputs JSON data containing the queried records. The structure includes:

  • records: An array of record objects, each containing the requested fields and their values.
  • returnAsItems flag in the output JSON indicates if records are returned as separate items or as a single array.

If Return as Items is enabled, each record is output as an individual item, allowing downstream nodes to process them one by one.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to the Fireberry API using an API key credential configured in n8n.
  • The node depends on Fireberry API endpoints to fetch objects, fields, dropdown values, and execute queries.
  • No additional external dependencies beyond the Fireberry API and n8n environment.

Troubleshooting

  • Empty Results: Ensure the object type and fields are correctly specified. Verify the query syntax if using advanced query mode.
  • Invalid Query Syntax: When using advanced query, errors may occur if the query string is malformed. Validate the query string against Fireberry's query language rules.
  • Field Loading Issues: If fields or dropdown values do not load, check API credentials and network connectivity.
  • Large Result Sets: Querying without a record limit may cause performance issues. Use the Record Limit property to restrict results.
  • Return as Items Misuse: Enabling Return as Items when expecting aggregated data can lead to unexpected workflow behavior. Use it only when individual record processing is needed.

Links and References

Discussion