FireberryTest icon

FireberryTest

Consume Fireberry API Test

Overview

The node integrates with the Fireberry API to perform batch updates on records of a specified object type. It allows users to update multiple records in one operation by specifying an array of record IDs along with the fields and their new values for each record.

This node is beneficial when you need to efficiently update many records at once without making individual update calls, saving time and reducing API request overhead. For example, if you have a list of customer records that require status changes or field corrections, you can use this node to apply all updates in a single batch operation.

Properties

Name Meaning
Object Type Selected A hidden boolean indicating whether an object type has been selected (true if selected, false otherwise).
Object Type Name or ID The Fireberry object type to update records for. Choose from a dropdown list or specify an ID via expression.
Records JSON array of records to update. Each item must include an id (record ID) and a record object containing field-value pairs to update. Format example: [{"id": "recordId", "record": {"Field1": "Value1", ...}}].

Output

The node outputs JSON data representing the result of the batch update operation. Typically, this will include confirmation of updated records or any relevant response data from the Fireberry API. The output structure corresponds to the API's response format for batch updates.

If the node supports binary data output, it would represent associated files or attachments related to the records, but based on the provided code and properties, the primary output is JSON data about the updated records.

Dependencies

  • Requires an API key credential for authenticating with the Fireberry API.
  • Depends on the Fireberry API service being accessible and properly configured.
  • Uses internal methods (executeUpdateBatchOperation) defined in the bundled methods module to perform the batch update logic.
  • The node expects the user to select or specify valid object types and record IDs available in Fireberry.

Troubleshooting

  • Common Issues:

    • Invalid or missing object type selection may cause errors.
    • Malformed JSON in the "Records" property can lead to parsing failures.
    • Providing non-existent record IDs will likely result in API errors.
    • Insufficient permissions or invalid API credentials will cause authentication failures.
  • Error Messages:

    • "The operation "updateBatch" is not supported!" — indicates an unsupported operation was requested; ensure the operation parameter is correctly set.
    • Errors related to invalid JSON input for records should be resolved by validating the JSON format.
    • API errors returned from Fireberry (e.g., unauthorized, not found) should be checked against your API key validity and object/record existence.

Links and References

  • n8n Expressions Documentation — for using expressions in property fields.
  • Fireberry API documentation (not provided here) — consult for detailed API behavior and batch update specifics.

Discussion