Fireberry icon

Fireberry

Consume Fireberry API

Overview

The node integrates with the Fireberry API to perform various data operations on Fireberry objects. Specifically, the "Create Batch" operation allows users to create multiple records in a single request for a specified object type. This is useful when you need to insert many records efficiently without making individual API calls for each record.

Common scenarios include:

  • Bulk importing data from external sources into Fireberry.
  • Creating multiple related records at once during automation workflows.
  • Migrating datasets or syncing batch updates from other systems.

Example: You have a list of customer records in JSON format and want to add them all to a Fireberry "Customer" object in one go.

Properties

Name Meaning
Object Type Name or ID The Fireberry object type where the records will be created. Choose from a dropdown or specify an ID.
Records A JSON array of records to create. Each record is an object with field names as keys and their values.

Example of Records property value (JSON):

{
  "data": [
    {
      "Key": "New Value"
    }
  ]
}

Output

The node outputs the result of the batch creation operation in the json output field. This typically includes information about the created records such as their IDs and any metadata returned by the Fireberry API.

If the Fireberry API supports returning binary data for this operation, it would be included accordingly, but based on the static code and properties, the output is primarily JSON data representing the created records.

Dependencies

  • Requires an API key credential for authenticating with the Fireberry API.
  • Depends on the Fireberry API being accessible and properly configured.
  • Uses internal methods (executeCreateBatchOperation) defined in the bundled source to handle the batch creation logic.
  • The node dynamically loads available object types and fields via helper methods (getObjects, getObjectFields).

Troubleshooting

  • Empty or invalid Object Type: Ensure that the "Object Type Name or ID" is selected or correctly specified; otherwise, the operation will fail.
  • Malformed Records JSON: The "Records" input must be valid JSON and follow the expected structure (an array of objects). Invalid JSON or incorrect structure will cause errors.
  • API Authentication Errors: Verify that the API key credential is set up correctly and has sufficient permissions.
  • Unsupported Operation Error: If the operation parameter is not set to "createBatch", the node throws an error indicating unsupported operation.
  • Partial Failures: If some records fail to create, check if the node is configured to continue on failure to handle partial success gracefully.

Links and References

Discussion