Fireberry icon

Fireberry

Interact with Fireberry Custom Objects

Overview

This node enables interaction with Fireberry custom objects, specifically allowing batch creation of multiple records within a specified custom object type. It is useful when you need to efficiently insert many records at once into Fireberry without making individual API calls for each record.

Typical use cases include:

  • Importing large datasets (e.g., contacts, deals) into Fireberry.
  • Synchronizing bulk data from other systems.
  • Automating mass data entry workflows.

For example, if you have an array of contact records in JSON format, you can use this node's Batch Create operation to add all those contacts to the "Contact" custom object in one request.

Properties

Name Meaning
Object Type The type of custom object to act on, e.g., Contact, Deal, etc.
Records A JSON-formatted array containing the data for multiple records to create in batch mode.

Output

The node outputs an array of JSON objects representing the results of the batch create operation. Each item corresponds to a created record and contains the response data returned by Fireberry for that record.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Fireberry API.
  • The node makes HTTP POST requests to Fireberry endpoints such as /api/v3/record/{objectType}/batch/create.
  • Proper configuration of the Fireberry API credentials in n8n is necessary.

Troubleshooting

  • Invalid JSON format for batch records: This error occurs if the "Records" input property does not contain valid JSON or is empty. Ensure the JSON array is correctly formatted and non-empty.
  • At least one record is required for batch create operation!: Triggered if the parsed records array is empty. Provide at least one record object.
  • Object Type field is required for batch create operation!: Make sure the "Object Type" property is set and not empty.
  • Error batch creating records in '{objectType}': Indicates an API error during the batch create call. Check network connectivity, API key validity, and Fireberry service status.
  • If the node fails but "Continue On Fail" is enabled, errors will be included in the output as error messages per item.

Links and References

Discussion