Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses 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 specified custom field and all its associated values from an account. It is useful in scenarios where you want to clean up or remove obsolete or incorrect custom fields from your data management system, ensuring that no residual data remains linked to the deleted field.
Practical examples include:
- Removing a deprecated custom field used for user preferences that are no longer relevant.
- Cleaning up custom fields after a data migration or restructuring process.
- Ensuring compliance by deleting sensitive custom fields and their data.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account from which the custom field will be deleted. |
| Custom Field Id | Identifier of the custom field to delete along with all its values. |
Output
The output JSON typically contains confirmation details about the deletion operation. This may include status messages or identifiers confirming that the custom field and its values were successfully removed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential or similar authentication token to authorize requests against the external service managing accounts and custom fields.
- The node depends on a REST API endpoint (base URL configured via credentials) that supports deleting custom fields.
- Proper configuration of the base URL and authentication credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Account Id or Custom Field Id can cause the operation to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity problems can prevent communication with the external API.
Error messages and resolutions:
- "Custom field not found": Verify that the Custom Field Id is correct and exists in the specified account.
- "Unauthorized" or "Authentication failed": Check that the API key or authentication token is valid and properly configured.
- "Account not found": Confirm the Account Id is accurate and accessible with the provided credentials.
- Timeout or network errors: Ensure stable internet connection and that the API endpoint is reachable.
Links and References
- Refer to the external service’s API documentation for detailed information on deleting custom fields.
- Consult n8n documentation on setting up API credentials and configuring HTTP request nodes for further customization.