Actions11
Overview
The node integrates with the Fireberry API to perform various operations on Fireberry objects and records. Specifically, the "Get Object Fields" operation retrieves all fields associated with a specified object type in Fireberry. This is useful when you want to dynamically discover the schema of an object type before querying or manipulating its data.
Common scenarios include:
- Fetching metadata about an object type to build dynamic queries.
- Displaying available fields for user selection in workflows.
- Automating integration tasks where field information is required to map data correctly.
For example, if you have an object type "Contact" in Fireberry, using this operation will return all fields like "FirstName", "LastName", "Email", etc., allowing you to use these fields in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Object Type Name or ID | The Fireberry object type to retrieve fields for. Choose from a dropdown list or specify an ID via expression. |
Output
The output JSON contains an array of field definitions for the specified object type. Each item in the output represents a field with details such as field name, type, label, and other metadata relevant to that field.
This allows workflows to programmatically access the structure of Fireberry objects.
The node does not output binary data for this operation.
Dependencies
- Requires connection to the Fireberry API.
- Requires an API authentication credential configured in n8n (an API key or token).
- Uses internal methods to load options dynamically from Fireberry (e.g.,
getObjectsandgetObjectFields).
Troubleshooting
Error: "The operation 'getObjectFields' is not supported!"
This indicates the operation parameter was set incorrectly or the node version does not support it. Ensure the operation is exactly "Get Object Fields".Empty or no fields returned
Verify that the specified object type exists in Fireberry and that the API credentials have sufficient permissions to read metadata.Authentication errors
Check that the API key/token credential is valid and properly configured in n8n.Load options not populating dropdowns
This can happen if the Fireberry API is unreachable or the credential is invalid. Confirm network connectivity and credential validity.
Links and References
- Fireberry API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- n8n Node Development Guide