Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Overview
This node operation deletes a specific custom field value associated with an account. It is useful in scenarios where you need to remove outdated or incorrect custom data entries linked to accounts, such as clearing deprecated tags, preferences, or metadata fields that are no longer relevant.
Practical examples include:
- Removing a custom attribute from a customer profile in a CRM system.
- Deleting a custom setting or flag previously assigned to an account.
- Cleaning up custom data fields during data maintenance or migration tasks.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which the custom field value will be deleted. |
| Custom Field Id | Identifier of the custom field that contains the value to be deleted. |
| Custom Field Value Id | Identifier of the specific custom field value to delete. |
Output
The output JSON typically contains the response from the API confirming the deletion of the custom field value. This may include status information or confirmation details indicating successful removal.
If the node supports binary data output (not evident here), it would represent any file or media related to the operation, but this operation primarily deals with JSON data.
Dependencies
- Requires an API key credential for authentication with the external service managing custom fields.
- The node uses a base URL configured in the credentials to send HTTP requests.
- Depends on the external API endpoint that handles custom field value deletions.
Troubleshooting
Common issues:
- Invalid or missing identifiers (Account Id, Custom Field Id, Custom Field Value Id) will cause the operation to fail.
- Authentication errors if the API key or credentials are not set correctly.
- Network or connectivity issues preventing access to the external API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly configured and has necessary permissions.
- "Not Found" or "Resource does not exist": Check that the provided IDs correspond to existing account, custom field, and value.
- "Bad Request": Ensure all required properties are provided and valid.
Links and References
- Refer to the external API documentation for managing custom fields and their values.
- n8n documentation on configuring API credentials and HTTP request nodes for further customization.