Actions7
- Custom Object Actions
Overview
This node enables interaction with Fireberry Custom Objects, specifically supporting batch update operations on these objects. The Batch Update operation allows users to update multiple records of a specified custom object type in one request by providing an array of record data in JSON format. This is particularly useful for scenarios where bulk modifications are needed, such as updating contact details for many customers or modifying deal statuses in a sales pipeline simultaneously.
Practical example: Suppose you have a list of customer records that need their email addresses updated after a domain change. Using this node's Batch Update operation, you can send all the updated records at once, improving efficiency and reducing API calls compared to updating each record individually.
Properties
Name | Meaning |
---|---|
Object Type | The type of custom object to act on (e.g., Contact, Deal). |
Records | A JSON-formatted array containing the records to update. Each record must include an id field along with other fields to update. |
Output
The output is a JSON array where each element corresponds to the result of the batch update operation. Each element typically contains the response data from Fireberry indicating the success or failure of updating the respective records.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Fireberry service.
- The node depends on the Fireberry API endpoints for batch updating records.
- Proper configuration of the Fireberry API credentials within n8n is necessary.
Troubleshooting
- Missing Object Type: If the "Object Type" property is not provided, the node will throw an error stating that this field is required.
- Invalid JSON Format: The "Records" property must be valid JSON. Invalid JSON will cause an error indicating the format issue.
- Missing Record IDs: Each record in the batch must include an
id
field. Omitting this will result in an error specifying that each record must have an 'id' for batch updates. - Credential Issues: If no valid API credentials are provided, the node will fail with an authentication error.
- Empty Records Array: Providing an empty array for records will trigger an error requiring at least one record.
- API Errors: Any errors returned from the Fireberry API during the batch update will be surfaced with messages indicating the failure reason.
To resolve these issues:
- Ensure the "Object Type" is correctly set.
- Validate the JSON syntax of the "Records" input.
- Confirm every record includes a valid
id
. - Verify that API credentials are configured and valid.
- Provide at least one record in the batch.
- Check API limits and permissions if API errors occur.
Links and References
- Fireberry API Documentation (for reference on batch update endpoint and payload structure)
- n8n Documentation on creating and using custom nodes and credentials