Fireberry

Overview

This node enables interaction with Fireberry custom objects, allowing users to perform various operations such as querying, creating, updating, and deleting records within specified custom object types. It supports both single and batch operations, making it suitable for managing data in Fireberry CRM or similar platforms that use custom objects.

Common scenarios include:

• Querying contacts, deals, or other custom entities with flexible filtering.
• Creating new records or updating existing ones programmatically.
• Deleting records individually or in bulk.
• Performing batch operations to efficiently handle multiple records at once.

Practical example:

• A marketing automation workflow could query "Contact" custom objects to segment leads based on specific criteria.
• A sales pipeline automation might update deal statuses in bulk after a certain event.
• Data cleanup workflows can delete outdated or invalid records from a custom object.

Properties

Note: Since the user requested only the "Default" operation under "Custom Object" resource, the above property is the one explicitly provided. However, the node supports many more properties depending on the operation (query, create, update, delete, batchCreate, batchUpdate, batchDelete), including fields like "Fields to Retrieve", "Query Type", "Record Data", "Record ID", "Records" (JSON array), and others.

Output

The node outputs an array of JSON objects representing the results of the performed operation:

• For query operations, the output contains the retrieved records matching the query criteria.
• For create, update, and delete operations, the output includes the response data confirming the success or details of the affected records.
• For batch operations, the output is an array of responses corresponding to each record processed.

The json output field holds these structured data objects. There is no indication that the node outputs binary data.

Dependencies

• Requires an API key credential for authenticating with the Fireberry API.
• Uses HTTP POST requests to Fireberry endpoints such as /api/query, /api/v3/record/{objectType}/batch/create, /api/v3/record/{objectType}/batch/update, and /api/v3/record/{objectType}/batch/delete.
• The node depends on internal helper functions (fireberryApiRequest and fireberryApiRequestAllItems) to communicate with the Fireberry API.
• Requires proper configuration of the Fireberry API credentials in n8n.

Troubleshooting

Common Issues

• Missing or invalid API credentials will cause authentication failures.
• Omitting required parameters such as "Object Type" or "Record ID" for relevant operations will throw errors.
• Invalid JSON format in batch operations' input fields will cause parsing errors.
• Providing empty or malformed queries may result in no data returned or API errors.

Error Messages and Resolutions

• "No valid credentials provided for Fireberry!": Ensure the API key credential is configured correctly in n8n.
• "Object Type field is required for [operation] operation!": Provide a valid custom object type string.
• "Record ID is required for [update/delete] operation!": Specify the record ID to update or delete.
• "At least one field is required for [create/update] operation!": Include at least one field name and value pair.
• "Invalid JSON format for batch records": Verify the JSON syntax in the batch records input.
• "Each record must have an 'id' field for batch update operation!": Ensure every record in batch update includes an id field.
• "At least one valid Record ID is required for batch delete operation!": Provide a comma-separated list of valid record IDs.

The node supports a "continue on fail" mode to allow workflows to proceed even if some items cause errors.

Links and References

• Fireberry API documentation (not included in source; consult Fireberry official docs)
• n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
• General REST API usage best practices