Fireberry icon

Fireberry

Interact with Fireberry Custom Objects

Actions7

Overview

This node enables interaction with Fireberry Custom Objects, specifically allowing querying of records from a specified custom object type. It supports two query methods: a visual query builder for constructing queries through a user-friendly interface, and an advanced mode where users can write raw Fireberry query syntax directly.

Common scenarios include:

  • Retrieving specific records or datasets from Fireberry custom objects such as Contacts, Deals, or other user-defined types.
  • Filtering records based on complex conditions using either the visual builder or advanced query strings.
  • Sorting and limiting results to optimize data retrieval for further processing in workflows.

Practical example:

  • A user wants to fetch all Contact records where the "status" field is "active" and the "last_contacted" date is within the last 30 days. They can use the visual query builder to set these conditions and retrieve only relevant fields sorted by creation date.

Properties

Name Meaning
Object Type The custom object type to act on (e.g., Contact, Deal). This specifies which Fireberry object you want to query.
Fields to Retrieve Comma-separated list of fields to retrieve from the object. Use * to select all fields.
Query Type Method to create the query:
- Visual Query Builder: Build query using a graphical interface.
- Advanced Query: Write a raw Fireberry query string directly.
Query (Shown if Query Type is Advanced) Raw Fireberry query string, e.g., ((field1 = value1) and (field2 is-not-null)).
Flattened Query Builder (Shown if Query Type is Visual Builder) Allows building a flattened query with multiple field conditions and logical operators (AND/OR), including grouping via parentheses. Supports operators like =, !=, <, >, contain, start-with, is-null, etc.
Limit Maximum number of records to return. Defaults to 100.
Sort By Field name to sort the results by. Defaults to createdon.
Sort Order Sort order direction:
- Ascending
- Descending (default)

Output

The node outputs an array of JSON objects representing the queried records. Each object corresponds to a record from the specified custom object type and contains the requested fields with their values.

  • The output field json contains the retrieved records.
  • No binary data output is produced by this operation.

Example output structure snippet:

[
  {
    "id": "record-id-123",
    "name": "John Doe",
    "email": "[email protected]",
    "status": "active",
    ...
  },
  ...
]

Dependencies

  • Requires an API key credential for authenticating with the Fireberry service.
  • The node makes HTTP POST requests to Fireberry's API endpoints to perform queries.
  • Proper configuration of the Fireberry API credentials in n8n is necessary before use.

Troubleshooting

  • Missing Object Type: If the "Object Type" property is empty or missing, the node will throw an error indicating that this field is required.
  • Invalid Query Syntax: For advanced queries, incorrect Fireberry query syntax may cause errors. Validate the query string carefully.
  • No Credentials Provided: The node requires valid Fireberry API credentials; otherwise, it will fail with an authentication error.
  • Empty or Invalid Query Conditions: Using the visual query builder incorrectly (e.g., no conditions or invalid operators) might result in empty or malformed queries.
  • Limit Exceeded: Requesting too many records without setting a limit may lead to performance issues or API rejections.
  • Error Messages: Errors returned from the Fireberry API are wrapped and presented with context, e.g., "Error querying 'Contact' objects". Check the message for details and verify API access and parameters.

To resolve common issues:

  • Ensure all required properties are filled correctly.
  • Verify API credentials and permissions.
  • Test queries independently in Fireberry to confirm syntax.
  • Use the visual query builder for simpler query construction if unsure about syntax.

Links and References

Discussion