Actions7
- Custom Object Actions
Overview
This node allows you to interact with Fireberry Custom Objects by performing various operations such as creating, querying, updating, and deleting records. It is particularly useful when you want to automate data management tasks within Fireberry's custom object system without manual intervention.
For the Create operation on a Custom Object, the node enables you to create a new record of a specified custom object type by providing field names and their corresponding values. This can be used in scenarios like adding new contacts, deals, or any other custom entity defined in Fireberry.
Practical example:
You have a "Contact" custom object in Fireberry and want to add a new contact automatically whenever a form is submitted on your website. Using this node, you specify the object type as "Contact" and provide the form data fields to create a new record seamlessly.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of the custom object to create a record in (e.g., Contact, Deal). |
| Record Data | A collection of fields representing the data for the new record. Each entry includes: |
| - Field Name: The name of the field to set. | |
| - Field Value: The value to assign to that field. |
Output
The output is a JSON array where each element corresponds to the result of creating a record. For the Create operation, the output contains the response data from Fireberry's API about the newly created record(s). This typically includes identifiers and any metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry API.
- The node depends on internal helper functions to make HTTP requests to Fireberry's REST API endpoints.
- Proper configuration of the Fireberry API credentials in n8n is necessary before using this node.
Troubleshooting
- Missing Object Type: If the "Object Type" property is empty or not provided, the node will throw an error indicating that this field is required.
- Empty Record Data: If no fields are provided in "Record Data," the node will raise an error stating that at least one field is required to create a record.
- Credential Issues: If the API credentials are missing or invalid, the node will fail with an authentication error.
- API Errors: Any errors returned by the Fireberry API during record creation will be surfaced as node errors with descriptive messages.
- JSON Parsing: For batch operations (not relevant here), invalid JSON input would cause errors; ensure proper formatting.
To resolve these issues:
- Always specify a valid object type.
- Provide at least one field with a name and value.
- Verify that the API credentials are correctly set up and valid.
- Check the API response messages for specific error details.
Links and References
- Fireberry API Documentation (Assumed URL for reference)
- n8n Documentation on Creating Custom Nodes
- General REST API usage best practices