Actions7
- Custom Object Actions
Overview
This node enables interaction with Fireberry Custom Objects, specifically allowing users to update records within a specified custom object type. It is useful in scenarios where you need to modify existing data entries in Fireberry, such as updating contact information, deal statuses, or any other custom object fields.
For example, if you have a "Contact" custom object and want to update the email address or phone number of a specific contact record, this node lets you specify the record by its ID and provide new field values to update.
Properties
| Name | Meaning |
|---|---|
| Object Type | The type of custom object to update (e.g., Contact, Deal). |
| Record ID | The unique identifier of the record to update. |
| Record Data | A collection of fields to update on the record. Each entry includes: |
| - Field Name: The name of the field to update. | |
| - Field Value: The new value for that field. |
Output
The node outputs an array of JSON objects representing the updated records returned from Fireberry after the update operation. Each object contains the updated data fields as confirmed by the Fireberry API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry service.
- The node makes HTTP POST requests to Fireberry's batch update endpoint
/api/v3/record/{objectType}/batch/update. - Proper configuration of the Fireberry API credentials in n8n is necessary.
Troubleshooting
- Missing Object Type: If the "Object Type" property is empty or missing, the node will throw an error indicating that this field is required.
- Missing Record ID: The node requires a valid "Record ID" to identify which record to update. An empty or whitespace-only ID will cause an error.
- Empty Record Data: At least one field must be provided in "Record Data" to perform an update; otherwise, an error is thrown.
- Invalid Credentials: If the Fireberry API credentials are not set or invalid, the node will fail with an authentication error.
- API Errors: Any errors returned from the Fireberry API during the update request will be surfaced as node errors with descriptive messages.
- JSON Format Issues: For batch operations (not applicable here but related), invalid JSON format in input can cause failures.
To resolve these issues:
- Ensure all required properties are filled correctly.
- Verify the API credentials are configured and valid.
- Check the Fireberry API documentation for correct usage and limits.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Fireberry API Documentation (for reference on endpoints and data formats)
- n8n Documentation on Custom Nodes and Credential Setup